Comment 2 for bug 1682773
Revision history for this message
| Riccardo Magrini (riccardo-magrini) wrote Re: issue during the deploy of service via Landscape | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
All lab environment has been realised using Ubuntu 16.04 LTS on VMware Esx. I'm testing Ubuntu Openstack Autopilot via conjure-up, the VM has been created on hypervisor in this way:
1 VM for MAAS + conjure-up (memory: 8GB, CPU: 1, HDD: 500TB);
1 VM for JUJU (memory: 8GB, CPU: 1, HDD: 500TB);
1 VM for LANDSCAPE (memory: 8GB, CPU: 1, HDD: 500TB);
1 VM for OPENSTACK1 (memory: 12GB, CPU: 1, HDD: 250GBx2) with 2vnic;
1 VM for OPENSTACK2 (memory: 12GB, CPU: 1, HDD: 250GBx2);
1 VM for OPENSTACK3 (memory: 12GB, CPU: 1, HDD: 250GBx2);
1 VM for OPENSTACK4 (memory: 12GB, CPU: 1, HDD: 250GBx2);
MAAS has 2 vnic:
eth0 10.20.81.0/24 (used for DHCP & DNS service)
eth1 10.20.82.0/24 (public)
until to LANDSCAPE everything works fine but after to run the deploy of Openstack I've reported the issue. Here the /var/log/syslog from each machines
log of node1 OPENSTACK1 http://
log of node1 OPENSTACK2 http://
log of node1 OPENSTACK3 http://
log of node1 OPENSTACK4 http://
the juju status is here https:/