[Openstack-operators] [OpenStack][Neutron][SFC] Regarding SFC support on provider VLAN N/W

[Amit Kumar]

Hi All,

We are using Ocata release and we have installed networking-sfc for Service
Function Chaining functionality. Installation was successful and then we
tried to create port pairs on VLAN N/W and it failed. We tried creating
port-pairs on VXLAN based N/W and it worked. So, is it that SFC
functionality is supported only on VXLAN based N/Ws?

Regards,
Amit
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [OpenStack-Operators][OpenStack] Regarding production grade OpenStack deployment

[Amit Kumar]

Hi,

Thanks for sharing your experience.

I am talking about HA of only OpenStack services and not the hosted
applications or the OpenStack instances they are hosted on. So, for now it
is not the requirement.

But from your response, it seems that you have deployed OpenStack with
Kolla-Ansible in multi node, multi-Controller architecture, right? And any
experience with Kolla-Ansible from OpenStack release upgrade perspective?
Is ZDT of OpenStack services feasible while upgrading?

Regards,
Amit

On May 18, 2018 5:48 PM, "Flint WALRUS" <gael.ther...@gmail.com> wrote:

Hi amit,

I’m using kolla-ansible as a solution on our own infrastructure, however,
be aware that because of the nature of Openstack you wont be able to
achieve zero downtime if your hosted application do not take advantage of
the distributed natre of ressources or if they’re not basically Cloud ready.

Cheers.
Le ven. 18 mai 2018 à 12:47, Amit Kumar <ebiib...@gmail.com> a écrit :

> Hi All,
>
> We want to deploy our private cloud using OpenStack as highly available
> (zero downtime (ZDT) - in normal course of action and during upgrades as
> well) production grade environment. We came across following tools.
>
>
>- We thought of using *Kolla-Kubernetes* as deployment tool, but we
>got feedback from Kolla IRC channel that this project is being retired.
>Moreover, we couldn't find latest documents having multi-node deployment
>steps and, High Availability support was also not mentioned at all anywhere
>in the documentation.
>- Another option to have Kubernetes based deployment is to use
>OpenStack-Helm, but it seems the OSH community has not made OSH 1.0
>officially available yet.
>- Last option, is to use *Kolla-Ansible*, although it is not a
>Kubernetes deployment, but seems to have good community support around it.
>Also, its documentation talks a little about production grade deployment,
>probably it is being used in production grade environments.
>
>
> If you folks have used any of these tools for deploying OpenStack to
> fulfill these requirements: HA and ZDT, then please provide your inputs
> specifically about HA and ZDT support of the deployment tool, based on your
> experience. And please share if you have any reference links that you have
> used for achieving HA and ZDT for the respective tools.
>
> Lastly, if you think we should think that we have missed another more
> viable and stable options of deployment tools which can serve our
> requirement: HA and ZDT, then please do suggest the same.
>
> Regards,
> Amit
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [OpenStack-Operators][OpenStack] Regarding production grade OpenStack deployment

[Amit Kumar]

Hi All,

We want to deploy our private cloud using OpenStack as highly available
(zero downtime (ZDT) - in normal course of action and during upgrades as
well) production grade environment. We came across following tools.


   - We thought of using *Kolla-Kubernetes* as deployment tool, but we got
   feedback from Kolla IRC channel that this project is being retired.
   Moreover, we couldn't find latest documents having multi-node deployment
   steps and, High Availability support was also not mentioned at all anywhere
   in the documentation.
   - Another option to have Kubernetes based deployment is to use
   OpenStack-Helm, but it seems the OSH community has not made OSH 1.0
   officially available yet.
   - Last option, is to use *Kolla-Ansible*, although it is not a
   Kubernetes deployment, but seems to have good community support around it.
   Also, its documentation talks a little about production grade deployment,
   probably it is being used in production grade environments.


If you folks have used any of these tools for deploying OpenStack to
fulfill these requirements: HA and ZDT, then please provide your inputs
specifically about HA and ZDT support of the deployment tool, based on your
experience. And please share if you have any reference links that you have
used for achieving HA and ZDT for the respective tools.

Lastly, if you think we should think that we have missed another more
viable and stable options of deployment tools which can serve our
requirement: HA and ZDT, then please do suggest the same.

Regards,
Amit
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

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

[Amit Kumar]

 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 following values for *compute_driver* and* virt_type*.

*[DEFAULT]*
*compute_driver = lxd.LXDDriver*
*[libvirt]*
*virt_type = lxc*

After this, I restarted the nova-compute service and launched an instance,
launch failed after some time (4-5 mins remain in spawning state) and gives
the following error:
[Error: No valid host was found. There are not enough hosts
available.]. Detailed
nova-compute logs are attached with this e-mail.

Could you please guide what else is required to launch container on
OpenStack setup? What other configurations will I need to configure LXD and
my nova user to see the LXD daemon.

Regards,
Amit


nova-compute.log
Description: Binary data
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [OpenStack][Ceph][Manila]

[Amit Kumar]

Hi All,

I have installed Ocata and configured Ceph storage cluster for shared file
system. I am able to mount a share created by Manila service, on a VM as
specified in following link:

https://docs.openstack.org/manila/ocata/devref/cephfs_native_driver.html

Problem is that I am only able to mount the share with ceph-fuse client
only, and when I am trying to mount it using ceph kernel client as follows:
*mount.ceph
192.168.121.110:6789:/volumes/_nogroup/f7ab60c0-cd28-4904-afd9-6da8057d1125
./mycephfs -o name=abc,secretfile=abc.secret*

I am getting the following error:
mount error 13 = Permission denied

Please suggest if anybody has also observed the same problem and let me
know there is any solution to this.

Regards,
Amit
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ceph @ OpenStack Sydney Summit

[AMIT KUMAR JAISWAL]

Hi Blair,

I'm interested in discussion on Ceph BoF and also added few points on
etherpad to discuss.

Looking forward to meet you and core team as well.

Thanks

KInd Regards
Amit Kumar Jaiswal
ᐧ

Amit Kumar Jaiswal
Mozilla Representative <http://reps.mozilla.org/u/amitkumarj441> | LinkedIn
<http://in.linkedin.com/in/amitkumarjaiswal1> | Portfolio
<http://amitkumarj441.github.io>
New Delhi, India
M : +91-8081187743 | T : @AMIT_GKP | PGP : EBE7 39F0 0427 4A2C








On Sun, Oct 29, 2017 at 5:43 PM, Blair Bethwaite <blair.bethwa...@gmail.com>
wrote:

> Hi all,
>
> (Apologies for the shotgun mail.)
>
> Following this up for anyone heading to Sydney in a week. I did end up
> getting a Ceph BoF on the program:
> https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20490
>
> If you have stuff you'd like to talk about, or especially share,
> please shout out and/or add to
> https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF.
>
> Also, hope to see some of the core team there!
>
> Cheers,
>
> On 7 July 2017 at 13:47, Blair Bethwaite <blair.bethwa...@gmail.com>
> wrote:
> > Hi all,
> >
> > Are there any "official" plans to have Ceph events co-hosted with
> OpenStack
> > Summit Sydney, like in Boston?
> >
> > The call for presentations closes in a week. The Forum will be organised
> > throughout September and (I think) that is the most likely place to have
> > e.g. Ceph ops sessions like we have in the past. Some of my local
> colleagues
> > have also expressed interest in having a CephFS BoF.
> >
> > --
> > Cheers,
> > ~Blairo
>
>
>
> --
> Cheers,
> ~Blairo
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Forum Reminder! Submissions due by Sept 29th

[AMIT KUMAR JAISWAL]

Hi Jimmy.

The above link you have given is broken and is saying "Internal Server
Error".

Please re-check the link again.

Thanks
Amit Kumar Jaiswal
ᐧ

Amit Kumar Jaiswal
Mozilla Representative <http://reps.mozilla.org/u/amitkumarj441> | LinkedIn
<http://in.linkedin.com/in/amitkumarjaiswal1> | Portfolio
<http://amitkumarj441.github.io>
New Delhi, India
M : +91-8081187743 | T : @AMIT_GKP | PGP : EBE7 39F0 0427 4A2C








On Mon, Sep 25, 2017 at 6:55 PM, Jimmy McArthur <ji...@openstack.org> wrote:

> Hello!
>
> This is a friendly reminder that all proposed Forum session leaders must
> submit their abstracts at:
>
> http://odsreg.openstack.org
>
> before 11:59PM UTC on Friday, September 29th!
>
> Cheers,
> Jimmy
>
>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ocata diskimage-builder heat issues

[Amit Kumar]

Hello,

Yes, my instance had os-collect-config service running. Unfortunately, I am
not having the same setup to see if /var/lib/heat-config/ is containing
deployment scripts or not but I remember I checked
/var/lib/cloud/instance/scripts/ was not having anything.

Regards,
Amit


On Thu, Jun 29, 2017 at 7:54 PM, Ignazio Cassano <ignaziocass...@gmail.com>
wrote:

> Hello Amit, tomorrow I'll try with trusty. Centos7 is working.
> Some questions:
> your instance created ny heat with SoftwareDeployment has
> os-collect-config runnig ?
> If yes, lauching os.refresh-config ang going under /var/lib/heat-config/
> on yoyr instance, you should see deployment scripts 
>
> Regards
> Ignazio
>
>
> 2017-06-29 13:47 GMT+02:00 Amit Kumar <ebiib...@gmail.com>:
>
>> Hi,
>>
>> I tried to create Ubuntu Trusty image using diskimage-builder tag 1.28.0,
>> dib-run-parts got included in VM os-refresh-config should have worked but
>> still SoftwareDeployment didn't work with the cloud image.
>>
>> Regards,
>> Amit
>>
>>
>> On Jun 29, 2017 5:08 PM, "Matteo Panella" <matteo.pane...@cnaf.infn.it>
>> wrote:
>>
>> On 29/06/2017 12:11, Ignazio Cassano wrote:
>> > Hello all,
>> > the new version of diskimage-builder (I am testing for centos 7) does
>> > not install dib-utils and jq in te image.
>> > The above are required by os-refresh-config .
>>
>> Yup, I reverted diskimage-builder to 2.2.0 (the last tag before
>> dib-run-parts was not injected anymore) and os-refresh-config works
>> correctly.
>>
>> os-refresh-config should probably be modified to depend on
>> dib-run-parts, however:
>> a) dib-run-parts provides package-style installation with an
>> RPM-specific package name
>> b) the package does not exist for Ubuntu 14.04 and there are no
>> source-style installation scripts
>>
>> Regards,
>> --
>> Matteo Panella
>> INFN CNAF
>> Via Ranzani 13/2 c - 40127 Bologna, Italy
>> Phone: +39 051 609 2903 <+39%20051%20609%202903>
>>
>>
>>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ocata diskimage-builder heat issues

[Amit Kumar]

Hi,

I tried to create Ubuntu Trusty image using diskimage-builder tag 1.28.0,
dib-run-parts got included in VM os-refresh-config should have worked but
still SoftwareDeployment didn't work with the cloud image.

Regards,
Amit

On Jun 29, 2017 5:08 PM, "Matteo Panella" 
wrote:

On 29/06/2017 12:11, Ignazio Cassano wrote:
> Hello all,
> the new version of diskimage-builder (I am testing for centos 7) does
> not install dib-utils and jq in te image.
> The above are required by os-refresh-config .

Yup, I reverted diskimage-builder to 2.2.0 (the last tag before
dib-run-parts was not injected anymore) and os-refresh-config works
correctly.

os-refresh-config should probably be modified to depend on
dib-run-parts, however:
a) dib-run-parts provides package-style installation with an
RPM-specific package name
b) the package does not exist for Ubuntu 14.04 and there are no
source-style installation scripts

Regards,
--
Matteo Panella
INFN CNAF
Via Ranzani 13/2 c - 40127 Bologna, Italy
Phone: +39 051 609 2903
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ocata diskimage-builder heat issues

[Amit Kumar]

Hi,

Probably the same problem I am facing. You replied on one of my e-mail
regarding SoftwareDeployment as well. Let me know if you find any working
working version of disk images builder.

Regards,
Amit

On Jun 28, 2017 10:26 PM, "Ignazio Cassano" 
wrote:

Hi All, last March I user diskimage builder tool to generate a centos7
image with tools for heat software deployment. That image worked fine with
heat software deployment in newton and works today with ocata.
Upgrading diskimage builder and creating again the image , heat software
deployment does not work because some errors in os-refresh-config .
I do not remember what version of diskimage builder I used in March. At
this time I am trying with 2.6.1 and 2.6.2 with same issues.
Does anyone know what is changed ?
Regards
Ignazio


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [telemetry] Issues with autoscaling using HEAT, Aodh and Ceilometer

[Amit Kumar]

Hi

I have installed OpenStack using OpenStack-Ansible 14.1.1. I have installed
Ceilometer, Aodh and using Mongo DB. I am trying simple autoscaling
scenario. On Horizon GUI, I have not been able to see the resource usage
getting updated consistently. In "ceilometer meter-list" command is also
not showing the update list of resources. In compute node ceilometer
polling, I am seeing log like *"Skip pollster cpu_util, no resources found
this cycle"*. Could you give any direction that what could be the issue?

Only couple of times, I have seen alarm state being changed to "alarm" from
"insufficient data" but at this point Aodh Notifier gives error:
*http://paste.openstack.org/show/612823/
*.

Please give some pointers to find the actual root cause behind the issues.

Regards,
Amit
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [openstack-operators] Regarding Ceilometer and Aodh service installation with OpenStack-Ansible

[Amit Kumar]

Hi All,

Please respond if anybody has installed Ceilometer and Aodh with
OpenStack-Ansible.

Regards,
Amit

On Mon, Jun 5, 2017 at 5:36 PM, Amit Kumar <ebiib...@gmail.com> wrote:

> Hi All,
>
> I have deployed OpenStack using Openstack-Ansible Newton 14.1.1 release.
> It works fine. On top of it when I re-deployed OpenStack (from scratch)
> with additional services Ceilometer and Aodh, Ceilometer service seems not
> working. "ceilometer meter-list" shows nothing. Have any of you folks
> deployed Ceilometer and Aodh especially with OpenStack-Ansible and does it
> work for you?
>
> On my setup, I have one Controller (Infra) node and three Compute nodes.
> And I am not using gnocchi but using mongodb.
>
> Regards,
> Amit
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [Openstack][Heat][Openstack-Ansible] Heat Engine not able to connect to Aodh Service

[Amit Kumar]

Hi All,

I have installed OpenStack Newton release using Ansible. I am trying
Orchestration with HEAT template. Here is the HEAT template I am using:
http://paste.openstack.org/show/610960/.

OS::Ceilometer:Alarm resource creation is failing while HEAT stack creation
is in progress. Here are the HEAT engine logs: http://paste.openstack.
org/show/610972/. They are showing error in connecting to
http://172.29.236.11:8042/v2/alarms but when I am trying to "wget
http://172.29.236.11:8042/v2/alarms; from the HEAT engine, it shows
connected but then "401 Unauthorized" response code.

Has anybody faced such problem, please respond?

Regards,
Amit
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [openstack][heat][openstack-telemetry][openstack-ansible] Heat engine unable to connect to Aodh service

[Amit Kumar]

Hi All,

I have installed OpenStack Newton release using Ansible. I am trying
Orchestration with HEAT template. Here is the HEAT template I am using:
http://paste.openstack.org/show/610960/.

OS::Ceilometer:Alarm resource creation is failing while HEAT stack creation
is in progress. Here are the HEAT engine logs:
http://paste.openstack.org/show/610972/. They are showing error in
connecting to http://172.29.236.11:8042/v2/alarms but when I am trying to
"wget http://172.29.236.11:8042/v2/alarms; from the HEAT engine, it shows
connected but then "401 Unauthorized" response code.

Has anybody faced such problem, please respond?

Regards,
Amit
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [openstack-ansible] Way to cleanup existing Openstack-Ansible deployment

[Amit Kumar]

Hi All,

I am trying to install Openstack Newton using OSA 14.0.8. Playbooks
setup-hosts.yml and setup-infrastructure.yml are getting stuck at some
point or other. Is there any way to cleanup everything which OSA has
deployed. I want to re-run all the playbooks as if I am doing a fresh
deployment.

Thanks.

Regards,
Amit
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [openstack][openstack-ansible] VMs not able to access external n/w

[Amit Kumar]

Hi All,

I have deployed Openstack Newton release using Openstack-Ansible 14.0.8
with target hosts (Controller and Compute) having Ubuntu 16.04. I want to
ping/access my external lab n/w through the VMs (instances in Openstack
Compute node) but not able to do so. Here are my environment and respective
configurations.

Basically, I had tried to create the example test n/w configuration (
https://docs.openstack.org/project-deploy-guide/openstack-ansible/newton/app-config-test.html#test-environment-config)
with
some changes in /etc/network/interfaces file because each Compute and
Controller Node are having two NICs in my setup. As per the example
environment, I am also having 1 Compute and 1 Controller Node in my setup.
Each physical node (Controller and Compute) is having two NICs. eth0 of
each machine is connected to a switch for any kind of communication b/w
compute and controller node. eth1 of each machine is connected to my lab
n/w (192.168.255.XXX). My */etc/network/interfaces* file from Controller
and Compute node are attached with this e-mail. I have also attached
*openstack_user_config.yml* file which I am using.

As my requirement is to provide external connectivity to VMs running inside
Openstack environment. Could you guys please have a look at my network
interfaces files and openstack_user_config.yml file to see if there is
anything wrong in these configurations which is blocking me in providing
the external connectivity to my VMs. Few things which might be helpful in
analyzing these files:

   - My lab n/w (192.168.255.XXX) is not tagged n/w, it doesn't expect VLAN
   tagged packets. So, do I need to create flat external n/w? As you can
   notice in my openstack_user_config.yml file, I have commented flat n/w
   section from provider networks section. It was done because when I first
   created this setup, I was unable to launch VMs and on discussion on
   openstack-ansible channel and looking at logs, it was found that "eth12"
   interface was non-existent on Compute node and hence error was appearing in
   logs. So, folks in openstack-ansible channel suggested to comment the flat
   n/w configuration from openstack_user_config.yml and re-configure neutron
   and give it a try. After this, I was able to launch VMs. But now with the
   requirement to ping/access outside lab n/w, it seems that flat n/w
   configuration would be required again. Please also suggest what changes are
   required to be made so that flat n/w configuration is also successful.
   - One more thing, if you look at my network interfaces file, br-vlan is
   having eth0 as bridge-port but my eth0 is not connected to the outside
   world i.e. lab n/w. Shouldn't br-vlan be using bridge-port as eth1 instead
   of eth0 considering that br-vlan is providing connectivity to external n/w?
   Now this may seem strange but when I am deleting eth0 from br-vlan and
   adding eth1 on br-vlan of both controller and compute node, these hosts are
   not reachable or able to ping (after some time) any other lab machine on
   192.168.255.XXX n/w and vice-versa whereas with having eth0 in br-vlan,
   compute and controller are able to access lab machines and vice-versa.


Just to include more information, if required, I am adding the commands I
used to create n/ws.
*My VMs are on INTERNAL_NET1 created using following commands:*
 - openstack network create --provider-network-type vlan INTERNAL_NET1
 - openstack subnet create INTERNAL_SUBNET_1_1 --network INTERNAL_NET1
--subnet-range 192.168.2.0/24

*EXTERNAL_NET is created using following commands:*
 - neutron net-create --provider:physical_network=flat
--provider:network_type=flat --shared --router:external=true GATEWAY_NET
 - neutron subnet-create GATEWAY_NET 192.168.255.0/24 --name GATEWAY_SUBNET
--gateway=192.168.255.1 --allocation-pool
start=192.168.255.81,end=192.168.255.100

* Earlier I had tried --provider:physical_network=vlan
--provider:network_type=vlan and things didn't work because lab n/w seems
not expecting VLAN tagged packets. So, thinking of having flat n/w now.*

*Router is created and GW and interfaces are set using following commands:*
 - neutron router-create NEUTRON-ROUTER
 - neutron router-gateway-set NEUTRON-ROUTER GATEWAY_NET
 - neutron router-interface-add NEUTRON-ROUTER INTERNAL_SUBNET_1_1

Thanks.

Regards,
Amit
# Controller Node (Infra).
# This illustrates the configuration of the first
# Infrastructure host and the IP addresses assigned should be adapted
# for implementation on the other hosts.
#
# After implementing this configuration, the host will need to be
# rebooted.

# Physical interface
auto eth0
iface eth0 inet manual

# Container/Host management VLAN interface
auto eth0.10
iface eth0.10 inet manual
vlan-raw-device eth0

# OpenStack Networking VXLAN (tunnel/overlay) VLAN interface
auto eth0.30
iface eth0.30 inet manual
vlan-raw-device eth0

# Storage network VLAN interface (optional)
auto eth0.20
iface eth0.20 inet manual
vlan-raw-device eth0

Re: [Openstack-operators] [Openstack] [Openstack-sdk] Error in making connection Openstack Python SDK

[Amit Kumar]

Thanks Michael for providing the code snippet. It was of great help. I was
doing things as expected but missed to set interface in profile.

Could you please provide some reference to what configparser object. I am
using code provided by you except setting config parser object and getting
SSL error when setting 'keystone' interface as 'public'. Error is pasted
here: http://paste.openstack.org/show/601428/

I am using auth_url as 'https://192.168.255.45:5000/v3'. 192.168.255.45 is
public interface. But when I am setting 'keystone' interface as 'internal'
with internal ip 172.29.236.11, connection is successful. Seems this SSL
error be related to config parser object.

Regards,
Amit


On Sat, Mar 4, 2017 at 2:12 AM, Michael Gale <gale.mich...@gmail.com> wrote:

> Hey,
>
> Here is how I am authenticating using openstacksdk:
>
> --snip--
> from openstack import connection
> from openstack import profile
> from openstack import utils
>
> def _create_connection(self, cloud_params, configobj):
>
> auth_args = {
> 'auth_url' : cloud_params['OS_AUTH_URL'],
> 'username' : cloud_params['OS_USERNAME'],
> 'password' : cloud_params['OS_PASSWORD'],
> 'project_name' : cloud_params['OS_PROJECT_NAME'],
> 'user_domain_name' : cloud_params['OS_USER_DOMAIN_NAME'],
> 'project_domain_name' : cloud_params['OS_USER_DOMAIN_NAME'],
> }
>
> prof = profile.Profile()
> prof.set_region(profile.Profile.ALL,
> cloud_params['OS_REGION_NAME'])
> prof.set_interface('identity', 'public')
>
> log.info("Authenticating against: %s" %
> (cloud_params['OS_AUTH_URL']))
> log.debug("Authenticating project: %s" % (cloud_params['OS_PROJECT_
> NAME']))
>
> conn = connection.Connection(
> profile=prof,
> verify=configobj.getboolean('DEFAULT', 'verify_certs'),
> user_agent='openstatstats',
> **auth_args
> )
>
> log.info("Authentication successful")
>
> return conn
> --snip--
>
> cloud_params is a dictionary with the OS_* vars loaded from the
> environment vars, configobj is a configparser object.
>
> Michael
>
>
>
> On Fri, Mar 3, 2017 at 4:12 AM, Amit Kumar <ebiib...@gmail.com> wrote:
>
>> Andy, thanks for your response.
>>
>> Address is reachable. I am running Horizon UI on this address
>> successfully. I used "http" whereas it should be "https" but it is not
>> working currently with https as well.
>>
>> Anyways, I tried the script from utility container where openstack
>> command line client is successful in executing the commands but python sdk
>> connection is failing with following error:
>>
>> *"openstack.exceptions.HttpException: HttpException: Expecting to find
>> domain in project - the server could not comply with the request since it
>> is either malformed or otherwise incorrect. The client is assumed to be in
>> error."*
>>
>> On noting the difference in wireshark traces, openstack command line
>> client is adding "domain" related information in request but this domain
>> related information is missing while attempting connection using python SDK.
>>
>> @openstack-sdk, could anyone provide information that how to add domain
>> related information while attempting connection using python sdk.
>>
>> Regards,
>> Amit
>>
>>
>> On Thu, Mar 2, 2017 at 8:54 PM, Andy McCrae <andy.mcc...@gmail.com>
>> wrote:
>>
>>> Hi Amit,
>>>
>>> Sending it again to include the ML!
>>>
>>> On 2 March 2017 at 11:01, Amit Kumar <ebiib...@gmail.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I have deployed Openstack using Openstack-Ansible. I am using Newton
>>>> release from tag 14.0.8. My test environment is containing only Compute
>>>> Node and Controller Node (Infra Node).
>>>> When using Openstack Python SDK, I am getting following error while
>>>> making connection to external_vib_lp_address (192.168.255.45) binded to
>>>> port 5000.
>>>>
>>>> *openstack.exceptions.SDKException: Connection failure that may be
>>>> retried.*
>>>>
>>>
>>> Based on the error this is a connection issue -  have you tested
>>> manually connecting to the external address you listed on that port?
>>> A good place to start would be to start looking at why it can't connect
>>> and seeing if you can manually connect outside of using

Re: [Openstack-operators] [Openstack-sdk] Error in making connection Openstack Python SDK

[Amit Kumar]

Andy, thanks for your response.

Address is reachable. I am running Horizon UI on this address successfully.
I used "http" whereas it should be "https" but it is not working currently
with https as well.

Anyways, I tried the script from utility container where openstack command
line client is successful in executing the commands but python sdk
connection is failing with following error:

*"openstack.exceptions.HttpException: HttpException: Expecting to find
domain in project - the server could not comply with the request since it
is either malformed or otherwise incorrect. The client is assumed to be in
error."*

On noting the difference in wireshark traces, openstack command line client
is adding "domain" related information in request but this domain related
information is missing while attempting connection using python SDK.

@openstack-sdk, could anyone provide information that how to add domain
related information while attempting connection using python sdk.

Regards,
Amit


On Thu, Mar 2, 2017 at 8:54 PM, Andy McCrae <andy.mcc...@gmail.com> wrote:

> Hi Amit,
>
> Sending it again to include the ML!
>
> On 2 March 2017 at 11:01, Amit Kumar <ebiib...@gmail.com> wrote:
>
>> Hi All,
>>
>> I have deployed Openstack using Openstack-Ansible. I am using Newton
>> release from tag 14.0.8. My test environment is containing only Compute
>> Node and Controller Node (Infra Node).
>> When using Openstack Python SDK, I am getting following error while
>> making connection to external_vib_lp_address (192.168.255.45) binded to
>> port 5000.
>>
>> *openstack.exceptions.SDKException: Connection failure that may be
>> retried.*
>>
>
> Based on the error this is a connection issue -  have you tested manually
> connecting to the external address you listed on that port?
> A good place to start would be to start looking at why it can't connect
> and seeing if you can manually connect outside of using the SDK.
>
> Are you trying to connect from a separate host to the OpenStack
> environment? If so can you even access 192.168.255.45?
>
> If you're still having issues feel free to jump into #openstack-ansible on
> Freenode and hopefully you'll be able to get more help there!
>
> Andy
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Error in making connection Openstack Python SDK

[Amit Kumar]

Thanks Alexandra. I missed to follow the convention. I will take care of it
in future.

But I am in doubt if this problem is specific to deployment using OSA or
some other generic problem.

Regards,
Amit

On Mar 2, 2017 4:35 PM, "Alexandra Settle" <a.set...@outlook.com> wrote:

> Hi Amit,
>
>
>
> I have CC’d Andy McCrae, the OpenStack-Ansible PTL.
>
>
>
> For all OpenStack-Ansible related queries, I would recommend tagging the
> subject line with [openstack-anisble] to help those with filters :)
>
>
>
> Either that, or potentially ask your question in the IRC channel
> #openstack-ansible
>
>
>
> Cheers,
>
>
>
> Alex
>
>
>
> *From: *Amit Kumar <ebiib...@gmail.com>
> *Date: *Thursday, March 2, 2017 at 11:01 AM
> *To: *Openstack <openst...@lists.openstack.org>, OpenStack Operators <
> openstack-operators@lists.openstack.org>
> *Subject: *[Openstack-operators] Error in making connection Openstack
> Python SDK
>
>
>
> Hi All,
>
>
>
> I have deployed Openstack using Openstack-Ansible. I am using Newton
> release from tag 14.0.8. My test environment is containing only Compute
> Node and Controller Node (Infra Node).
>
> When using Openstack Python SDK, I am getting following error while making
> connection to external_vib_lp_address (192.168.255.45) binded to port 5000.
>
>
>
> *openstack.exceptions.SDKException: Connection failure that may be
> retried.*
>
>
>
> Any clue about this issue? More detailed traces are at:
> http://paste.openstack.org/show/601053/
>
>
>
> Python script which I am using for this purpose is attached with this
> e-mail.
>
>
>
> Thanks.
>
>
>
> Regards,
>
> Amit
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Error in making connection Openstack Python SDK

[Amit Kumar]

Hi All,

I have deployed Openstack using Openstack-Ansible. I am using Newton
release from tag 14.0.8. My test environment is containing only Compute
Node and Controller Node (Infra Node).
When using Openstack Python SDK, I am getting following error while making
connection to external_vib_lp_address (192.168.255.45) binded to port 5000.

*openstack.exceptions.SDKException: Connection failure that may be retried.*

Any clue about this issue? More detailed traces are at:
http://paste.openstack.org/show/601053/

Python script which I am using for this purpose is attached with this
e-mail.

Thanks.

Regards,
Amit
from openstack import connection

auth_args = {
'auth_url': 'http://192.168.255.45:5000/v3',
'project_name': 'admin',
'username': 'admin',
'password': '362a7f371d10d4461659e049548',
}
conn = connection.Connection(**auth_args)

projects = conn.identity.find_project('admin')
print projects

#network = conn.network.find_network("jenkins")
#print network___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [openstack] Unable to launch an instance

[Amit Kumar]

Thanks you all for your responses.

Problem is resolved at my end with the help of folks in #openstack-ansible
chat room. Problem was in my yml configuration file where a non-existent
interface was specified.

Regards,
Amit

On Wed, Mar 1, 2017 at 12:24 AM, Kris G. Lindgren <klindg...@godaddy.com>
wrote:

> You should look at the compute node and the scheduler for actual error
> logs as said below.
>
>  But one things I see is that you are using qcow2 images, but have disk in
> your flavor set to zero.  Seems like the problem is that your image is
> larger than the virtual disk that you are creating via your flavor.  Does
> booting a VM using a default flavor work?
>
>
> ___
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
> On 2/28/17, 11:26 AM, "Mikhail Medvedev" <mihail...@gmail.com> wrote:
>
> On Tue, Feb 28, 2017 at 11:49 AM, Amit Kumar <ebiib...@gmail.com>
> wrote:
> > Hi All,
> >
> > I have installed Openstack Newton using Openstack-Ansible. While
> creating an
> > instance, it is failing with following error:
> >
> > MessageNo valid host was found. There are not enough hosts
>
> The "not enough hosts" could be due to any number of reasons. To know
> exactly why, check your /var/log/nova/nova-scheduler.log on
> controller. The error means that nova scheduler was not able to find
> any suitable hosts to boot the VM. It could be for example because you
> are using a flavor that does not fit, or because your compute node
> appears dead to controller. In any case, nova scheduler log should
> make it a bit clearer.
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack-operators
>
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [openstack] Unable to launch an instance

[Amit Kumar]

Hi All,

I have installed Openstack Newton using Openstack-Ansible. While creating
an instance, it is failing with following error:

*Message**No valid host was found. There are not enough hosts available.*
*Code**500**Details**File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/nova/conductor/manager.py",
line 496, in build_instances context, request_spec, filter_properties) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/nova/conductor/manager.py",
line 567, in _schedule_instances hosts =
self.scheduler_client.select_destinations(context, spec_obj) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/nova/scheduler/utils.py",
line 370, in wrapped return func(*args, **kwargs) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/nova/scheduler/client/__init__.py",
line 51, in select_destinations return
self.queryclient.select_destinations(context, spec_obj) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/nova/scheduler/client/__init__.py",
line 37, in __run_method return getattr(self.instance, __name)(*args,
**kwargs) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/nova/scheduler/client/query.py",
line 32, in select_destinations return
self.scheduler_rpcapi.select_destinations(context, spec_obj) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/nova/scheduler/rpcapi.py",
line 126, in select_destinations return cctxt.call(ctxt,
'select_destinations', **msg_args) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/oslo_messaging/rpc/client.py",
line 169, in call retry=self.retry) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/oslo_messaging/transport.py",
line 97, in _send timeout=timeout, retry=retry) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py",
line 464, in send retry=retry) File
"/openstack/venvs/nova-14.0.8/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py",
line 455, in _send raise result*

I executed following commands before launching an instance.

   1.
*openstack image create --disk-format qcow2 --container-format bare
   --public --file ./cirros-0.3.4-x86_64-disk.img cirros0.3.4-image *
   2.
*openstack flavor create --public m1.extra_tiny --id auto --ram 2048 --disk
   0 --vcpus 1 --rxtx-factor 1 *
   3.
*openstack network create net1 *
   4. *openstack subnet create subnet1 --network net1 --subnet-range
   192.168.2.0/24 *

*/var/log/nova/nova-compute.log* are showing are something like this:

*2017-02-28 23:11:44.610 1142 INFO nova.compute.resource_tracker
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Auditing locally
available compute resources for node compute1*
*2017-02-28 23:11:44.721 1142 WARNING nova.scheduler.client.report
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] No authentication
information found for placement API. Placement is optional in Newton, but
required in Ocata. Please enable the placement service before upgrading.*
*2017-02-28 23:11:44.721 1142 WARNING nova.scheduler.client.report
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Unable to refresh my
resource provider record*
*2017-02-28 23:11:44.800 1142 INFO nova.compute.resource_tracker
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Total usable vcpus: 8,
total allocated vcpus: 0*
*2017-02-28 23:11:44.800 1142 INFO nova.compute.resource_tracker
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Final resource view:
name=compute1 phys_ram=7877MB used_ram=2048MB phys_disk=908GB used_disk=2GB
total_vcpus=8 used_vcpus=0 pci_stats=[]*
*2017-02-28 23:11:44.896 1142 WARNING nova.scheduler.client.report
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Unable to refresh my
resource provider record*
*2017-02-28 23:11:44.896 1142 INFO nova.compute.resource_tracker
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Compute_service record
updated for compute1:compute1*
*2017-02-28 23:12:30.611 1142 WARNING nova.virt.libvirt.imagecache
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Unknown base file:
/var/lib/nova/instances/_base/3451088abe875a7f691a9e229d767aa128dc0da3*
*2017-02-28 23:12:30.612 1142 INFO nova.virt.libvirt.imagecache
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Removable base files:
/var/lib/nova/instances/_base/3451088abe875a7f691a9e229d767aa128dc0da3*
*2017-02-28 23:12:30.612 1142 INFO nova.virt.libvirt.imagecache
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Base or swap file too
young to remove:
/var/lib/nova/instances/_base/3451088abe875a7f691a9e229d767aa128dc0da3*
*2017-02-28 23:12:45.609 1142 INFO nova.compute.resource_tracker
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Auditing locally
available compute resources for node compute1*
*2017-02-28 23:12:45.750 1142 WARNING nova.scheduler.client.report
[req-ad2fc0ae-e98f-45c5-89cc-3211a69a37ec - - - - -] Unable to refresh my
resource provider record*
*2*

*nova service-list* is showing 

Re: [Openstack-operators] OSA Newton Release Deployment in test environment

[Amit Kumar]

Thanks to all for your responses.

It is resolved. Actually, I am installing Infra and Compute on my
virtualbox VMs. Both these VMs are having NAT adapter and this was giving
IP to VM in the same subnet as was being assigned to containers in Infra
node. Ultimately, routing rules at Infra node were conflicting. Changed the
subnet of NAT adapter of my Infra VM and it worked.

Regards,
Amit

On Feb 6, 2017 11:52 PM, "Jesse Pretorius" <jesse.pretor...@rackspace.co.uk>
wrote:

> LXC will setup eth0 in the container which will NAT through the host to
> access the internet.
>
>
>
> Clearly there’s something wrong with that traffic path, so step through it
> like you would with any environment by validating that it is able to reach
> its gateway (host), then next hop, etc.
>
>
>
> *From: *Amit Kumar <ebiib...@gmail.com>
> *Date: *Monday, February 6, 2017 at 8:17 AM
> *To: *gustavo panizzo <g...@zumbi.com.ar>
> *Cc: *"openstack-operators@lists.openstack.org" <
> openstack-operators@lists.openstack.org>
> *Subject: *Re: [Openstack-operators] OSA Newton Release Deployment in
> test environment
>
>
>
> Error is because LXC repo container on infra node is not having
> connectivity to internet and is unable to download these packages. Thing is
> that why containers are not having connectivity to internet whereas infra
> node is having connectivity to internet.
>
>
>
> Any idea if this is a general behavior that LXC containers are not able to
> reach internet?
>
>
>
> On Mon, Feb 6, 2017 at 1:39 PM, gustavo panizzo <g...@zumbi.com.ar> wrote:
>
> On Sat, Feb 04, 2017 at 11:52:10PM +0530, Amit Kumar wrote:
> > Hi All,
> >
> > used.\nWARNING: The following packages cannot be authenticated!\n
>
> dpkg/apt are telling you what the problem is, go to the server and fix
> apt
>
>
> > python-pkg-resources python-setuptools\n", "stdout_lines": ["Reading
> > package lists...", "Building dependency tree...", "Reading state
> > information...", "The following extra packages will be installed:", "
> > python-pkg-resources", "Suggested packages:", " python-openssl-doc
> > python-openssl-dbg python-distribute", " python-distribute-doc doc-base",
> > "The following NEW packages will be installed:", " python-openssl
> > python-pkg-resources python-pyasn1 python-setuptools", "0 upgraded, 4
> newly
> > installed, 0 to remove and 4 not upgraded.", "Need to get 418 kB of
> > archives.", "After this operation, 1801 kB of additional disk space will
> be
>
> > used.", "WARNING: The following packages cannot be authenticated!", "
> > python-pkg-resources python-setuptools"]}
> same error again
>
>
> --
> 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
>
> keybase: https://keybase.io/gfa
>
>
>
> --
> Rackspace Limited is a company registered in England & Wales (company
> registered number 03897010) whose registered office is at 5 Millington
> Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy
> can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail
> message may contain confidential or privileged information intended for the
> recipient. Any dissemination, distribution or copying of the enclosed
> material is prohibited. If you receive this transmission in error, please
> notify us immediately by e-mail at ab...@rackspace.com and delete the
> original message. Your cooperation is appreciated.
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] OSA Newton Release Deployment in test environment

[Amit Kumar]

Error is because LXC repo container on infra node is not having
connectivity to internet and is unable to download these packages. Thing is
that why containers are not having connectivity to internet whereas infra
node is having connectivity to internet.

Any idea if this is a general behavior that LXC containers are not able to
reach internet?

On Mon, Feb 6, 2017 at 1:39 PM, gustavo panizzo <g...@zumbi.com.ar> wrote:

> On Sat, Feb 04, 2017 at 11:52:10PM +0530, Amit Kumar wrote:
> > Hi All,
> >
> > used.\nWARNING: The following packages cannot be authenticated!\n
>
> dpkg/apt are telling you what the problem is, go to the server and fix
> apt
>
>
> > python-pkg-resources python-setuptools\n", "stdout_lines": ["Reading
> > package lists...", "Building dependency tree...", "Reading state
> > information...", "The following extra packages will be installed:", "
> > python-pkg-resources", "Suggested packages:", " python-openssl-doc
> > python-openssl-dbg python-distribute", " python-distribute-doc doc-base",
> > "The following NEW packages will be installed:", " python-openssl
> > python-pkg-resources python-pyasn1 python-setuptools", "0 upgraded, 4
> newly
> > installed, 0 to remove and 4 not upgraded.", "Need to get 418 kB of
> > archives.", "After this operation, 1801 kB of additional disk space will
> be
>
> > used.", "WARNING: The following packages cannot be authenticated!", "
> > python-pkg-resources python-setuptools"]}
> same error again
>
>
> --
> 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
>
> keybase: https://keybase.io/gfa
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] OSA Newton Release Deployment in test environment

[Amit Kumar]

Thanks Salman. But in my case MTU sizes are same.

Anybody having any other opinion on this?

Regards,
Amit

On Sun, Feb 5, 2017 at 2:13 AM, Salman Toor <salman.t...@it.uu.se> wrote:

>
> <https://mail.uu.se/owa/?ae=PreFormAction=ReplyAll=IPM.Note=RgAYgm11jTMZSqDNQIKZhLPSBwCZtICTEb9DQLldDzcg6sC7DML5AACZtICTEb9DQLldDzcg6sC7AABJX%2fCxAAAJ=_1486240160008_300721368#>
> Hi,
>
> I am not an expert but I had similar problem and that was because of
> different MTU at host interface and container's interface.
>
> My suggestion will be to check the MTU, if that helps.
>
> Regards..
> Salman.
>
>
> PhD, Scientific Computing
> Researcher, IT Department,
> Uppsala University.
> Senior Cloud Architect,
> SNIC.
> Cloud Application Expert,
> UPPMAX.
> salman.t...@it.uu.se
> <https://mail.uu.se/owa/redir.aspx?REF=m0Eyh6bAe3V0K5jcrZeIkUVJw4_716jYUS9Yd1fJMFOsyyE71yXTCAFtYWlsdG86c2FsbWFuLnRvb3JAaXQudXUuc2U.>
> http://www.it.uu.se/katalog/salto690
> --
> *From:* Amit Kumar [ebiib...@gmail.com]
> *Sent:* Saturday, February 04, 2017 7:22 PM
> *To:* openstack-operators@lists.openstack.org
> *Subject:* [Openstack-operators] OSA Newton Release Deployment in test
> environment
>
> Hi All,
>
> I am trying to prepare test environment as mentioned in the following
> link. I am using two VMs created in Virtualbox. One will be Infra Node and
> other will be Compute Node. "Block Storage Host" is not present in my
> deployment.
> http://docs.openstack.org/project-deploy-guide/
> openstack-ansible/newton/app-config-test.html#test-environment-config
>
> While following instructions in Newton deployment guide (
> http://docs.openstack.org/project-deploy-guide/openstack-ansible/newton/),
> at "Run Playbooks" step, "openstack-ansible setup-hosts.yml" is successful
> but "openstack-ansible setup-infrastructure.yml" is failing.
>
> It is failing for " infra1_repo_container-" and is failing at "TASK
> [pip_install : Install apt packages] **
> "
> Here is the failure text:
> failed: [infra1_repo_container-f9649c00] (item=[u'build-essential',
> u'python-setuptools', u'libffi-dev', u'libssl-dev', u'python-dev',
> u'python-openssl', u'python-pyasn1']) => {"cache_update_time": 0,
> "cache_updated": false, "failed": true, "invocation": {"module_args":
> {"allow_unauthenticated": false, "autoremove": false, "cache_valid_time":
> null, "deb": null, "default_release": null, "dpkg_options":
> "force-confdef,force-confold", "force": false, "install_recommends": null,
> "name": ["build-essential", "python-setuptools", "libffi-dev",
> "libssl-dev", "python-dev", "python-openssl", "python-pyasn1"],
> "only_upgrade": false, "package": ["build-essential", "python-setuptools",
> "libffi-dev", "libssl-dev", "python-dev", "python-openssl",
> "python-pyasn1"], "purge": false, "state": "latest", "update_cache": false,
> "upgrade": null}, "module_name": "apt"}, "item": ["build-essential",
> "python-setuptools", "libffi-dev", "libssl-dev", "python-dev",
> "python-openssl", "python-pyasn1"], "msg": "'/usr/bin/apt-get -y -o
> \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\"
> install 'python-setuptools' 'python-openssl' 'python-pyasn1'' failed: E:
> There are problems and -y was used without --force-yes\n", "stderr": "E:
> There are problems and -y was used without --force-yes\n", "stdout":
> "Reading package lists...\nBuilding dependency tree...\nReading state
> information...\nThe following extra packages will be installed:\n
> python-pkg-resources\nSuggested packages:\n python-openssl-doc
> python-openssl-dbg python-distribute\n python-distribute-doc doc-base\nThe
> following NEW packages will be installed:\n python-openssl
> python-pkg-resources python-pyasn1 python-setuptools\n0 upgraded, 4 newly
> installed, 0 to remove and 4 not upgraded.\nNeed to get 418 kB of
> archives.\nAfter this operation, 1801 kB of additional disk space will be
> used.\nWARNING: The following packages cannot be authenticated!\n
> python-pkg-resources python-setuptools\n", "stdout_lines": ["Reading
> package lists...", "Building de

[Openstack-operators] OSA Newton Release Deployment in test environment

[Amit Kumar]

Hi All,

I am trying to prepare test environment as mentioned in the following link.
I am using two VMs created in Virtualbox. One will be Infra Node and other
will be Compute Node. "Block Storage Host" is not present in my deployment.
http://docs.openstack.org/project-deploy-guide/openstack-ansible/newton/app-config-test.html#test-environment-config

While following instructions in Newton deployment guide (
http://docs.openstack.org/project-deploy-guide/openstack-ansible/newton/),
at "Run Playbooks" step, "openstack-ansible setup-hosts.yml" is successful
but "openstack-ansible setup-infrastructure.yml" is failing.

It is failing for " infra1_repo_container-" and is failing at "TASK
[pip_install : Install apt packages] **"
Here is the failure text:
failed: [infra1_repo_container-f9649c00] (item=[u'build-essential',
u'python-setuptools', u'libffi-dev', u'libssl-dev', u'python-dev',
u'python-openssl', u'python-pyasn1']) => {"cache_update_time": 0,
"cache_updated": false, "failed": true, "invocation": {"module_args":
{"allow_unauthenticated": false, "autoremove": false, "cache_valid_time":
null, "deb": null, "default_release": null, "dpkg_options":
"force-confdef,force-confold", "force": false, "install_recommends": null,
"name": ["build-essential", "python-setuptools", "libffi-dev",
"libssl-dev", "python-dev", "python-openssl", "python-pyasn1"],
"only_upgrade": false, "package": ["build-essential", "python-setuptools",
"libffi-dev", "libssl-dev", "python-dev", "python-openssl",
"python-pyasn1"], "purge": false, "state": "latest", "update_cache": false,
"upgrade": null}, "module_name": "apt"}, "item": ["build-essential",
"python-setuptools", "libffi-dev", "libssl-dev", "python-dev",
"python-openssl", "python-pyasn1"], "msg": "'/usr/bin/apt-get -y -o
\"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\"
install 'python-setuptools' 'python-openssl' 'python-pyasn1'' failed: E:
There are problems and -y was used without --force-yes\n", "stderr": "E:
There are problems and -y was used without --force-yes\n", "stdout":
"Reading package lists...\nBuilding dependency tree...\nReading state
information...\nThe following extra packages will be installed:\n
python-pkg-resources\nSuggested packages:\n python-openssl-doc
python-openssl-dbg python-distribute\n python-distribute-doc doc-base\nThe
following NEW packages will be installed:\n python-openssl
python-pkg-resources python-pyasn1 python-setuptools\n0 upgraded, 4 newly
installed, 0 to remove and 4 not upgraded.\nNeed to get 418 kB of
archives.\nAfter this operation, 1801 kB of additional disk space will be
used.\nWARNING: The following packages cannot be authenticated!\n
python-pkg-resources python-setuptools\n", "stdout_lines": ["Reading
package lists...", "Building dependency tree...", "Reading state
information...", "The following extra packages will be installed:", "
python-pkg-resources", "Suggested packages:", " python-openssl-doc
python-openssl-dbg python-distribute", " python-distribute-doc doc-base",
"The following NEW packages will be installed:", " python-openssl
python-pkg-resources python-pyasn1 python-setuptools", "0 upgraded, 4 newly
installed, 0 to remove and 4 not upgraded.", "Need to get 418 kB of
archives.", "After this operation, 1801 kB of additional disk space will be
used.", "WARNING: The following packages cannot be authenticated!", "
python-pkg-resources python-setuptools"]}

On looking around, it seems that it is happening because LXC are lacking
connectivity to internet. So, as per the link:
http://docs.openstack.org/developer/openstack-ansible/developer-docs/installation-hosts-limited-connectivity.html
I tried the step mentioned at this page under heading "Install pip through
deployment host" but it is giving following error.

"fatal: [infra1]: FAILED! => {"changed": true, "cmd": "python
/opt/get-pip.py --isolated --no-index --find-links=/tmp/pip_install
 pip==8.1.2 setuptools==28.6.0 wheel==0.29.0", "delta": "0:00:00.740516",
"end": "2017-02-04 22:58:12.985852", "failed": true, "invocation":
{"module_args": {"_raw_params": "python /opt/get-pip.py --isolated
--no-index --find-links=/tmp/pip_install  pip==8.1.2 setuptools==28.6.0
wheel==0.29.0", "_uses_shell": true, "chdir": null, "creates": null,
"executable": null, "removes": null, "warn": true}, "module_name":
"command"}, "rc": 1, "start": "2017-02-04 22:58:12.245336", "stderr": "Url
'/tmp/pip_install' is ignored. It is either a non-existing path or lacks a
specific scheme.\n  Url '/tmp/pip_install' is ignored. It is either a
non-existing path or lacks a specific scheme.\n  Could not find a version
that satisfies the requirement setuptools==28.6.0 (from versions: )\nNo
matching distribution found for setuptools==28.6.0", "stdout": "Requirement
already up-to-date: pip==8.1.2 in
/usr/local/lib/python2.7/dist-packages\nCollecting setuptools==28.6.0",
"stdout_lines": ["Requirement already up-to-date: pip==8.1.2 in