@MaLeiOnline we have a working version of Jupiter v5.0 in the following branch. This version is a lot easier to use, and the top-level readme provides some new instructions. It does not, however, have instructions on setting up k8s. about jupiter

[MuleiOnline]

When we deploy the V5.0, In the step of running launch_mapper.py. We meet the error below. Also we found that the port 8081 and 8888 is not working. How do to fix it? Thanks!

`joinus@host:~/Jupiter-finalccdag/core$ python launch_mapper.py

namespace/jason-mapper created
INFO:launch_mapper.py:Starting to deploy HEFT (a single home pod)
DEBUG:launch_mapper.py:Home service created. status = '{'load_balancer': {'ingress': None}}'
DEBUG:launch_mapper.py:HEFT home deployment created. status = '{'available_replicas': None,
'collision_count': None,
'conditions': None,
'observed_generation': None,
'ready_replicas': None,
'replicas': None,
'unavailable_replicas': None,
'updated_replicas': None}'
INFO:launch_mapper.py:Successfully deployed HEFT
INFO:launch_mapper.py:Waiting for HEFT pod to boot...
Starting to serve on 127.0.0.1:8081
DEBUG:launch_mapper.py:Trying to get the assignment from HEFT mapper
INFO:launch_mapper.py:mapping:
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "error trying to reach service: dial tcp 10.244.166.145:8888: i/o timeout",
"code": 500
}`

[jasonatran]

It It takes about 15 minutes for DRUPE to gather enough statistics about the network so that the HEFT mapper can query it and output a mapping. To make life easier, you are welcome to skip the task mapping step and launch tasks on a k8s cluster using a self-designated mapping. That is, you can manually set which k8s node to launch a Jupiter task on. You can do this by creating your own json. There are examples of this json in the core/samples/ folder. mapping_example.json is a mapping you can use for launching the application laid out in in app_specific_files/example/app_config.yaml.