I am trying to create a multi-node setup by following devstack guide. Setup: I have a base Ubuntu14 laptop running 2 virtualbox based ubuntu16 VMs: "controller" and "compute1". I intentionally disabled nova-compute service on controller just to see a server instance getting created on the compute1 node. But instance creation fails and I see the following in nova scheduler service logs: 2017-01 ...
[root@controller1 ~ (keystone_adminv3)]# openstack project create admin Conflict occurred attempting to store project - it is not permitted to have two projects with the same name in the same domain : admin (HTTP 409) (Request-ID: req-250236d8-88ff-4931-951a-8444cff1243a) it seeems that the project is present but i cannot see it. Any suggestions?
The current Horizon settings indicate no valid image creation methods are available. Providing an image location and/or uploading from the local file system must be allowed to support image creation - Ask OpenStack: Q&A Site for OpenStack Users and Developers ALL UNANSWERED Ask Your Question 1
Hi team, i'm new to openstack, i've been working on vmware esxi for last 3 years now, as part of new project i should have knowledge of openstack, so i joined you. Previously i heard of it but not paid much concentrations, i just want to know main diffe between vmware esxi and openstack, is openstack vmware sort of software or any thing different. please let me know, thanks in advance.
However, when launched through openstack (devstack), networking does not seem to be initialized properly. The Horizon GUI reports that the VM has been assigned Public 172.24.4.230.
The router instance has both NICs attached to br-int and both uses separate vlan ids. Wondering how to untag the external facing NIC (vlan=0) as the public subnet 'public-flat-subnet' is getting a vlan id > 0, and my external lan 192.168.15.0/24 is untagged? stefws ( 2018-03-01 01:31:41 -0500 ) edit
I'm having trouble creating an instance (openstack server create --flavor small --image cirros provider-instance12240 ) My cinder node's log return such errors and the instance is being created with status "error" (actually not being created):
Of course, it happend when i was trying to start the neutron server. The server doesn't start. The other servers written in document on website were started without problem as bellows. # systemctl restart openstack-nova-api.service openstack-nova-scheduler.service \ openstack-nova-conductor.service Then , I tried to start next step as bellows.
