Hi Kanagaraj,
After discuss with Multi-Cloud team, the VIM information is merged with
cloud-region. You can find the esr-system-info from cloud-region.
Thanks,
LiZi
原始邮件
发件人:
收件人:李滋00164331
Hi Dear HelpDesk,
The Jenkins job encountered an issues which seems to be related
to nexus repo’s provision. It reported “Access denied to:
Hi Jess,
Sorry that I missed the previous invitation.
Please also invite me as committer for following projects:
multicloud/openstack
multicloud/openstack/windriver
Thanks.
Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile
Hi Jess,
Sorry that I missed the previous invitation.
Please also invite me as committer for following projects:
multicloud/openstack
multicloud/openstack/windriver
Thanks.
Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile
Hi Subhash,
I don’t think you can directly add relationship with service-subscription
without giving details of customer.
In relationship-data add one more key value pair for your customer.
If you have edge allowed between tenant and service-subscription then it will
surely work.
Just add
Dear LiZi,
I have referred your aai patch and for VIM, it does not have any modeling
information init.
Any reason why VIM is not included ?
Regards
Kanagaraj M
***
Dear Gildas,
I think for deployment projects both HEAT template (demo) and OOM, it would
make it easier if every component in Amsterdam release would follow the same
versioning , 1.1.
Otherwise, deployment services needs to keep track of the version of each
component, which would complicate
Hi Steven,
For the VF-C APIs, We have the link in wiki, they are in HTML format that
generated by Swagger. It need time to convert it to readthedocs format.
We are now looking through the documentation Guidelines and call for
volunteers to do this. I will feedback to you if this work has
Hi,
After confirming the name list with each projects, Suggest to use Open Lab
JIRA to keep track the the process of remotely accessary accounts creation.
link here
https://jira.onap.org/secure/RapidBoard.jspa?projectKey=OPENLABS=67=planning
Hi David and OOM Team,
I'm glad to let you know that oom registrator has been successfully deployed in
k8s cluster which filled the last part of map. Now every ONAP microservices
deployed by OOM will be automatically registered to MSB by oom registrator, and
microservices can leverage MSB
Looks like it could have been a glitch.
both are fixed now..
Thansk!
Jess
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
11 matches
Mail list logo