[Openstack] Release Naming for S - time to suggest a name!

Hey everybody, Once again, it is time for us to pick a name for our "S" release. Since the associated Summit will be in Berlin, the Geographic Location has been chosen as "Berlin" (State). Nominations are now open. Please add suitable names to https://wiki.openstack.org/wiki/Release_Naming/S_Pro

Re: [Openstack] Openstack data replication

For example, you can have 3 replicas stored in a global cluster and get dispersion across multiple geographic regions. But it's all one logical cluster. With container sync, you've got separate clusters with their own durability characteristics. So you would have eg 3 replicas in each cluster, m

Re: [Openstack] [openstack] [pike]

no, everywhere its "controller" now. On Tue, Feb 20, 2018 at 10:56 PM, nithish B wrote: > Wait. Why does it say curl -g -i -X GET http://controller:35357/v3/ -H > "Accept: application/json" - shouldn't it be your "h > ttp://nagraj_controller:35357/v3/ ."? > >

Re: [Openstack] [openstack] [pike]

Wait. Why does it say curl -g -i -X GET http://controller:35357/v3/ -H "Accept: application/json" - shouldn't it be your "http://nagraj_controller: 35357/v3/ ."? Regards, Nitish B. On Tue, Feb 20, 2018 at 11:54 AM, Guru Desai wrote: > Here you go with the out

Re: [Openstack] [openstack] [pike]

Here you go with the output : [root@controller ~]# openstack --debug endpoint list START with options: [u'--debug', u'endpoint', u'list'] options: Namespace(access_key='', access_secret='***', access_token='***', access_token_endpoint='', access_token_type='', auth_type='', auth_url=' http://cont

Re: [Openstack] [openstack] [pike]

According to your bootstrap and auth file, you're using http://controller:35357/v3, but the error you posted said http://nagraj_controller:35357/v3/. Run this: openstack --debug endpoint list Paste the output in here. -Erik On Tue, Feb 20, 2018 at 11:22 AM, Guru Desai wrote: > yes, did the bo

Re: [Openstack] Openstack data replication

Hi All, Any reference or information with regards to how sync process in global clusters is more efficient than container sync in openstack swift. Aravind M D On Mon, Feb 19, 2018 at 11:41 AM, aRaviNd wrote: > Thanks John. > > You mentioned sync process in global clusters is more efficient. Co

Re: [Openstack] [openstack] [pike]

yes, did the bootstrap commands and everything went fine i.e no errors. admin port 35357 as mentioned in the pike install guide for keystone.. keystone-manage bootstrap --bootstrap-password ADMIN_PASS *\* --bootstrap-admin-url http://controller:35357/v3 *\* --bootstrap-internal-url http://contr

Re: [Openstack] [openstack] [pike]

Why are you auth on the admin port? Try the default 5000? > On Feb 20, 2018, at 7:58 AM, Erik McCormick > wrote: > > Did you run all the keystone-manage bootstrap commands? This looks > like you're trying to create the domain you're supposed to be > authenticating against. > > On Tue, Feb 20,

Re: [Openstack] [openstack] [pike]

Did you run all the keystone-manage bootstrap commands? This looks like you're trying to create the domain you're supposed to be authenticating against. On Tue, Feb 20, 2018 at 10:34 AM, Guru Desai wrote: > Hi Nithish, > > That part is verified. Below is the snippet of the rc file > > export OS_U

Re: [Openstack] [openstack] [pike]

Hi Nithish, That part is verified. Below is the snippet of the rc file export OS_USERNAME=admin export OS_PASSWORD=ADMIN_PASS export OS_PROJECT_NAME=admin export OS_USER_DOMAIN_NAME=Default export OS_PROJECT_DOMAIN_NAME=Default export OS_AUTH_URL=http://controller:35357/v3 export OS_ID

Re: [Openstack] [nova] [nova-lxd] Query regarding LXC instantiation using nova

Hi Amit (re-titled thread with scoped topics) As Matt has already referenced, [0] is a good starting place for using the nova-lxd driver. On Tue, 20 Feb 2018 at 11:13 Amit Kumar wrote: > Hello, > > I have a running OpenStack Ocata setup on which I am able to launch VMs. > But I want to move to

Re: [Openstack] [openstack] [pike]

Hi Guru, This looks more like a problem of finding the credentials. Please check if you sourced the credentials, and you did it right. A sample source parameters might look like the following: export OS_USERNAME=admin export OS_PASSWORD= export OS_TENANT_NAME=admin export OS_AUTH_URL=https://nagar

[Openstack] [openstack][openstack-nova][openstack-operators] Query regarding LXC instantiation using nova

Hello, I have a running OpenStack Ocata setup on which I am able to launch VMs. But I want to move to LXC instantiation instead of VMs. So, for this, I installed nova-compute-lxd on my compute node (Ubuntu 16.04). */etc/nova/nova-compute.conf* on my compute nodes was changed to contain the follow

[Openstack] [openstack] [pike]

Hi I am trying to install openstack pike and following the instruction mentioned in https://docs.openstack.org/keystone/pike/install/keystone-install-rdo.html for installing keystone. I am done with the environment setup. But after installing keystone, tried to create a project as mentioned in the