date:20170302

[Openstack-operators] Upcoming Ops Midcycle

2017-03-02 Thread Melvin Hillsman

Hey everyone,

If you have been getting previous emails then you are aware the midcycle is
quickly approaching; March 15th and 16th!

*T**here is still time offer feedback for existing sessions*. Also remember
that *you do not have to be in attendance to have a voice here*. We welcome
you to participate in shaping the dialogue even though you may not
physically attend.

Below you will find all the etherpads for each session and there are no
hard and fast rules so feel free to throw as many ideas in there as you can
think of. Please also *encourage other Operators, End-Users, Application
Developers, Developers, everyone you know who can offer some value to
participate*.

https://etherpad.openstack.org/p/MIL-ops-openstack-on-containers
https://etherpad.openstack.org/p/MIL-ops-containers-on-openstack
https://etherpad.openstack.org/p/MIL-ops-logging-and-monitoring
https://etherpad.openstack.org/p/MIL-ops-ceph-and-cephfs
https://etherpad.openstack.org/p/MIL-ops-baremetal
https://etherpad.openstack.org/p/MIL-ops-upgrades-patches-packaging
https://etherpad.openstack.org/p/MIL-ops-config-management
https://etherpad.openstack.org/p/MIL-ops-keystone-and-authentication
https://etherpad.openstack.org/p/MIL-ops-inventory-and-fleet-management
https://etherpad.openstack.org/p/MIL-ops-live-migration
https://etherpad.openstack.org/p/MIL-ops-security
https://etherpad.openstack.org/p/MIL-ops-scaling-and-tuning
https://etherpad.openstack.org/p/MIL-ops-deployment-methods
https://etherpad.openstack.org/p/MIL-ops-rabbitmq-pitfalls-ha
https://etherpad.openstack.org/p/MIL-ops-dbaas-with-trove
https://etherpad.openstack.org/p/MIL-ops-do-not-do
https://etherpad.openstack.org/p/MIL-ops-osops
https://etherpad.openstack.org/p/MIL-ops-fault-injection-and-remediation
https://etherpad.openstack.org/p/MIL-ops-migration-onboarding-end-user-experience
https://etherpad.openstack.org/p/MIL-ops-ux-horizon-cli
https://etherpad.openstack.org/p/MIL-ops-cellsv2
https://etherpad.openstack.org/p/MIL-ops-neutron
https://etherpad.openstack.org/p/MIL-ops-cinder-rolling-upgrade
https://etherpad.openstack.org/p/MIL-ops-overview-of-auc
https://etherpad.openstack.org/p/MIL-ops-uc
https://etherpad.openstack.org/p/MIL-ops-capacity-management
https://etherpad.openstack.org/p/MIL-ops-manila
https://etherpad.openstack.org/p/MIL-ops-telco-nfv

-- 
Kind regards,

Melvin Hillsman
Ops Technical Lead
OpenStack Innovation Center

mrhills...@gmail.com
phone: (210) 312-1267
mobile: (210) 413-1659
http://osic.org

Learner | Ideation | Belief | Responsibility | Command
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Operators Mid-cycle Moderator

2017-03-02 Thread Robert Starmer

Melvin,

I don't see anywhere on the meetup page defining who has been assigned to
moderate what?  Is there a document describing this yet?

Robert

On Sat, Feb 25, 2017 at 9:35 AM, Melvin Hillsman 
wrote:

> Hey everyone,
>
> Thank you all for signing up to be moderators at the upcoming Operator
> Mid-cycle. I am sending this not only to you but to the ML at large in
> hopes that we get additional volunteers.
>
> *OpenStack Community:*
>
> Please sign up if you are interested in moderating using the following
> etherpad - https://etherpad.openstack.org/p/MIL-ops-meetup
>
> And * there is still time to suggest additional sessions and +1 or -1
> existing sessions*. Also remember that *you do not have to be in
> attendance to have a voice here*. We welcome you to participate in
> shaping the agenda even though you may not physically attend.
>
> *Current Volunteer Moderators:*
>
> If you have not already, be sure to take a look at the moderator's guide
> -  https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide
>
> What I hope to accomplish with this email is that you 1) respond back
> confirming that you will or will not attend the mid-cycle if you have not
> already confirmed, and 2) the agenda is just about done and some names have
> been added to sessions already. If you do not feel comfortable with a
> session you have been assigned, go ahead and change. If you see an open
> session and would like to moderate it, feel free to add your name.
>
> I created an etherpad for each session on the agenda and dropped in a
> template on each one - https://etherpad.openstack.org/p/MIL-ops-moderator-
> template - please be sure to start working out the details of the session.
>
> *I encourage each moderator to use this thread to ask any questions and
> reach out to the community at large and projects related to the session you
> are moderating.*
>
> I am looking forward to seeing all of you at the mid-cycle and thank you
> so much for your time.
>
> --
> Kind regards,
>
> Melvin Hillsman
> Ops Technical Lead
> OpenStack Innovation Center
>
> mrhills...@gmail.com
> phone: (210) 312-1267
> mobile: (210) 413-1659
> http://osic.org
>
> Learner | Ideation | Belief | Responsibility | Command
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Operators Mid-cycle Moderator

2017-03-02 Thread Matt Jarvis

I am definitely coming, and will moderate anywhere we need. I'm
particularly interested in monitoring, lifecycle mgmt and ceph but happy to
help anywhere.

On 25 Feb 2017 18:36, "Melvin Hillsman"  wrote:

> Hey everyone,
>
> Thank you all for signing up to be moderators at the upcoming Operator
> Mid-cycle. I am sending this not only to you but to the ML at large in
> hopes that we get additional volunteers.
>
> *OpenStack Community:*
>
> Please sign up if you are interested in moderating using the following
> etherpad - https://etherpad.openstack.org/p/MIL-ops-meetup
>
> And * there is still time to suggest additional sessions and +1 or -1
> existing sessions*. Also remember that *you do not have to be in
> attendance to have a voice here*. We welcome you to participate in
> shaping the agenda even though you may not physically attend.
>
> *Current Volunteer Moderators:*
>
> If you have not already, be sure to take a look at the moderator's guide
> -  https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide
>
> What I hope to accomplish with this email is that you 1) respond back
> confirming that you will or will not attend the mid-cycle if you have not
> already confirmed, and 2) the agenda is just about done and some names have
> been added to sessions already. If you do not feel comfortable with a
> session you have been assigned, go ahead and change. If you see an open
> session and would like to moderate it, feel free to add your name.
>
> I created an etherpad for each session on the agenda and dropped in a
> template on each one - https://etherpad.openstack.org/p/MIL-ops-moderator-
> template - please be sure to start working out the details of the session.
>
> *I encourage each moderator to use this thread to ask any questions and
> reach out to the community at large and projects related to the session you
> are moderating.*
>
> I am looking forward to seeing all of you at the mid-cycle and thank you
> so much for your time.
>
> --
> Kind regards,
>
> Melvin Hillsman
> Ops Technical Lead
> OpenStack Innovation Center
>
> mrhills...@gmail.com
> phone: (210) 312-1267
> mobile: (210) 413-1659
> http://osic.org
>
> Learner | Ideation | Belief | Responsibility | Command
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Operators Mid-cycle Moderator

2017-03-02 Thread Nick Jones

Hi Melvin.

> On 25 Feb 2017, at 17:35, Melvin Hillsman  wrote:
> 
> Hey everyone,
> 
> Thank you all for signing up to be moderators at the upcoming Operator 
> Mid-cycle. I am sending this not only to you but to the ML at large in hopes 
> that we get additional volunteers.

[..]

> What I hope to accomplish with this email is that you 1) respond back 
> confirming that you will or will not attend the mid-cycle if you have not 
> already confirmed, and 2) the agenda is just about done and some names have 
> been added to sessions already. If you do not feel comfortable with a session 
> you have been assigned, go ahead and change. If you see an open session and 
> would like to moderate it, feel free to add your name.

I’m absolutely still attending and have added myself as a moderator for the 
security session.  Thanks for pulling this together.

Cheers and see you all there!

— 

-Nick
-- 
DataCentred Limited registered in England and Wales no. 05611763

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

[Openstack-operators] Fwd: [openstack-dev] [tc][swg][all] Leadership training sign-up is open!

2017-03-02 Thread Shamail Tahir

FYI, in case you missed this on the openstack-dev mailing list. Great
opportunity.

-- Forwarded message --
From: Colette Alexander 
Date: Thu, Mar 2, 2017 at 3:16 PM
Subject: [openstack-dev] [tc][swg][all] Leadership training sign-up is open!
To: "OpenStack Development Mailing List (not for usage questions)" <
openstack-...@lists.openstack.org>

Hello Stackers!

We're opening up the sign-up sheet for leadership training beyond the TC,
Board and Foundation staff to the whole community.

What: Leadership Training, customized for members of the OpenStack Community
When: April 11/12/13
Where: ZingTrain, in Ann Arbor, Michigan.

If you can confirm your ability to attend, please sign up here:
https://etherpad.openstack.org/p/Leadershiptraining

There are a lot of details on that etherpad about timing, place,
recommended locations to stay, etc. You can also scroll down to read a
sample itinerary of subjects covered in the training. If you have any
questions at all, feel free to ask questions in this thread, or in
#openstack-swg as many folks who lurk in that channel have attended.

Some quick notes:

   - This is the exact same training that was done last year
   - We're planning on having 1-2 people attend who also attended training
   last year to give some context and continuity to the discussions.
   - The training costs are fully funded by the Foundation, and attendees
   only need to cover the cost of travel, lodging, and some meals (breakfast
   and lunch during training is provided).
   - We're capping attendance at 20 people.
   - I'd like to finalize our list by March 24th, so please start the work
   of getting travel approvals, etc., now.

If there are any past attendees who'd like to chime in in response to this
to discuss your experiences with training, please do! Please feel free to
ping me on IRC (I'm gothicmindfood) if you have any other questions.

Thanks so much,

-colette/gothicmindfood

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Forum Brainstorming???

2017-03-02 Thread Shamail Tahir

Thanks Stig.  I added your etherpad to the wiki page[1].

[1] https://wiki.openstack.org/wiki/Forum/Boston2017#Team-specific

On Wed, Mar 1, 2017 at 5:13 AM, Stig Telfer 
wrote:

> Thanks Shamail -
>
> We’ve just completed a first pass on our brainstorming in the Scientific
> WG.  Some ideas from a research computing perspective are here:
>
> https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg
>
> More input from WG members (and anyone else) is of course welcome and
> appreciated.
>
> Best wishes,
> Stig
>
>
> > On 27 Feb 2017, at 20:38, Shamail Tahir  wrote:
> >
> > Hi everyone,
> >
> > Welcome to the topic selection process for our first Forum in Boston. If
> you've participated in an ops meetup before, this should seem pretty
> comfortable. If not, note that this is not a classic conference track with
> speakers and presentations. OpenStack community members (participants in
> development teams, working groups, and other interested individuals)
> discuss the topics they want to cover and get alignment on and we welcome
> your participation.
> >
> > The Forum is for the entire community to come together; create a neutral
> space rather than having separate “ops” and “dev” days. Boston marks the
> start of the Queen's release cycle, where ideas and requirements will be
> gathered. Users should aim to come armed with feedback from February's
> Ocata release if at all possible. We aim to ensure the broadest coverage of
> topics that will allow for multiple parts of the community getting together
> to discuss key areas within our community/projects.
> >
> > Examples of the types of discussions and some sessions that might fit
> within each one:
> >   • Strategic, whole-of-community discussions, to think about the
> big picture, including beyond just one release cycle and new technologies
> >   • eg Making OpenStack One Platform for containers/VMs/Bare Metal
> (Strategic session) the entire community congregates to share opinions on
> how to make OpenStack achieve its integration engine goal
> >   • Cross-project sessions, in a similar vein to what has happened
> at past design summits, but with increased emphasis on issues that are
> relevant to all areas of the community
> >   • eg Rolling Upgrades at Scale (Cross-Project session) – the Large
> Deployments Team collaborates with Nova, Cinder and Keystone to tackle
> issues that come up with rolling upgrades when there’s a large number of
> machines.
> >   • Project-specific sessions, where developers can ask users
> specific questions about their experience, users can provide feedback from
> the last release and cross-community collaboration on the priorities, and
> ‘blue sky’ ideas for the next release.
> >   • eg Neutron Pain Points (Project-Specific session) – Co-organized
> by neutron developers and users. Neutron developers bring some specific
> questions they want answered, Neutron users bring feedback from the latest
> release and ideas about the future.
> >
> > There are two stages to the brainstorming:
> > 1. Starting today, set up an etherpad with your group/team, or use
> one on the list and start discussing ideas you'd like to talk about at the
> Forum. Then, through +1s on etherpads and mailing list discussion, work out
> which ones are the most needed - just like you did prior to the ops events.
> > 2. Then, in a couple of weeks, we will open up a more formal
> web-based tool for submission of abstracts that came out of the
> brainstorming on top.
> >
> > We expect working groups may make their own etherpads, however the User
> Committee offers a catch-all to get the widest feedback possible:
> > https://etherpad.openstack.org/p/BOS-UC-brainstorming
> >
> > Feel free to use that, or make one for your group and add it to the list
> at: https://wiki.openstack.org/wiki/Forum/Boston2017
> >
> > Thanks,
> > User Committee
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] (openstack-ansible) Mitaka 13.3.12 failing to report correct resource usage

2017-03-02 Thread Jesse Pretorius

From: "Craft, Mike" 
Date: Thursday, March 2, 2017 at 7:50 PM
To: "openstack-operators@lists.openstack.org" 

Subject: [Openstack-operators] (openstack-ansible) Mitaka 13.3.12 failing to 
report correct resource usage

Hello,

Did an upgrade from liberty to mitaka and we are experiencing an issue where 
the audit of locally available compute resource usage is not seeing instances 
that were deployed prior to the upgrade. Has anyone experienced this before? We 
hard power cycled all the vms (and hypervisor) to make sure they are running on 
the latest nova version. This is impacting scheduling of resources/quota usage 
as you could imagine ☺

If you look in the nova database, can you see those instances there? From the 
look of things, your hypervisor has no instances allocated to it in its 
database. I hope that you have a backup! ☺

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] (openstack-ansible) Mitaka 13.3.12 failing to report correct resource usage

2017-03-02 Thread Craft, Mike

Hello,

Did an upgrade from liberty to mitaka and we are experiencing an issue where 
the audit of locally available compute resource usage is not seeing instances 
that were deployed prior to the upgrade. Has anyone experienced this before? We 
hard power cycled all the vms (and hypervisor) to make sure they are running on 
the latest nova version. This is impacting scheduling of resources/quota usage 
as you could imagine ☺

Example from one box.

2017-03-02 19:37:52.189 17586 INFO nova.compute.resource_tracker 
[req-da808a51-f9e3-4762-b46b-ee313183d2d2 - - - - -] Auditing locally available 
compute resources for node usw1comp024.openstack.local
2017-03-02 19:37:54.413 17586 INFO nova.compute.resource_tracker 
[req-da808a51-f9e3-4762-b46b-ee313183d2d2 - - - - -] Total usable vcpus: 56, 
total allocated vcpus: 0
2017-03-02 19:37:54.413 17586 INFO nova.compute.resource_tracker 
[req-da808a51-f9e3-4762-b46b-ee313183d2d2 - - - - -] Final resource view: 
name=hostname.openstack.local phys_ram=257725MB used_ram=2048MB 
phys_disk=4433GB used_disk=2GB total_vcpus=56 used_vcpus=0 pci_stats=[]

virsh list --all
IdName   State

2 instance-18ed  running
3 instance-18ea  running
4 instance-18e4  running
5 instance-18de  running
6 instance-076f  running
7 instance-0420  running

libvirt+  7995  1.6  0.2 13401648 653416 ? Sl   19:07   0:40 
/usr/bin/qemu-system-x86_64 -name instance-18ed -S -machine 
pc-i440fx-trusty,accel=kvm,usb=off -cpu 
SandyBridge,+invpcid,+erms,+bmi2,+smep,+avx2,+bmi1,+fsgsbase,+abm,+pdpe1gb,+rdrand,+f16c,+osxsave,+movbe,+dca,+pcid,+pdcm,+xtpr,+fma,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
 -m 8192 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 
d306091c-e1a6-44ef-b5ff-bc412c4b2341 -smbios type=1,manufacturer=OpenStack 
Foundation,product=OpenStack 
Nova,version=13.1.3,serial=03000200-0400-0500-0006-000700080009,uuid=d306091c-e1a6-44ef-b5ff-bc412c4b2341,family=Virtual
 Machine -no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-18ed.monitor,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew 
-global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on 
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 
file=/var/lib/nova/instances/d306091c-e1a6-44ef-b5ff-bc412c4b2341/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,discard=ignore
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=27 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:bc:3c:ee,bus=pci.0,addr=0x3 
-chardev 
file,id=charserial0,path=/var/lib/nova/instances/d306091c-e1a6-44ef-b5ff-bc412c4b2341/console.log
 -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 
-device isa-serial,chardev=charserial1,id=serial1 -chardev pty,id=charchannel0 
-device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
 -spice port=5900,addr=10.60.16.73,disable-ticketing,seamless-migration=on -k 
en-us -device 
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
libvirt+  8516  1.6  0.2 13401672 594804 ? Sl   19:07   0:39 
/usr/bin/qemu-system-x86_64 -name instance-18ea -S -machine 
pc-i440fx-trusty,accel=kvm,usb=off -cpu 
SandyBridge,+invpcid,+erms,+bmi2,+smep,+avx2,+bmi1,+fsgsbase,+abm,+pdpe1gb,+rdrand,+f16c,+osxsave,+movbe,+dca,+pcid,+pdcm,+xtpr,+fma,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
 -m 8192 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 
2e3cdf87-5022-45df-8a47-150afee1ca83 -smbios type=1,manufacturer=OpenStack 
Foundation,product=OpenStack 
Nova,version=13.1.3,serial=03000200-0400-0500-0006-000700080009,uuid=2e3cdf87-5022-45df-8a47-150afee1ca83,family=Virtual
 Machine -no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-18ea.monitor,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew 
-global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on 
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 
file=/var/lib/nova/instances/2e3cdf87-5022-45df-8a47-150afee1ca83/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,discard=ignore
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=28 -device 
virtio-net-pci,n

[Openstack-operators] [Fault Genes] WG Weekly Meeting

2017-03-02 Thread Nematollah Bidokhti

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Nematollah Bidokhti:MAILTO:nematollah.bidok...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='openstack
 -operat...@lists.openstack.org':MAILTO:openstack-operators@lists.openstack
 .org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='user-comm
 it...@lists.openstack.org':MAILTO:user-commit...@lists.openstack.org
DESCRIPTION;LANGUAGE=en-US:\n\n\n  Meeting Conference Link: https://www
 .connectmeeting.att.com\n  Meeting Number: 8887160594\n  Code: 377
 3562\n  USA Toll-Free: 888-716-0594\n  USA Caller Paid: 215-861-61
 99\nFor Other Countries:Click Here to View Global Conference A
 ccess Numbers\n\n\n\nThe link to the wiki
  https://wiki.openstack.org/wiki/Fault_Genes_Working_Group\n\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TH;WKST=SU
SUMMARY;LANGUAGE=en-US:[Fault Genes] WG Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160519T09
DTEND;TZID=Pacific Standard Time:20160519T10
UID:04008200E00074C5B7101A82E00850B72A929FAAD101000
 0100028E111C3B604D445920643DCDC32B7B2
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170302T184701Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:198
LOCATION;LANGUAGE=en-US:Conference Call
X-MICROSOFT-CDO-APPT-SEQUENCE:198
X-MICROSOFT-CDO-OWNERAPPTID:1315723232
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [Fault Genes] WG Weekly Meeting

2017-03-02 Thread Nematollah Bidokhti

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Nematollah Bidokhti:MAILTO:nematollah.bidok...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='openstack
 -operat...@lists.openstack.org':MAILTO:openstack-operators@lists.openstack
 .org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='user-comm
 it...@lists.openstack.org':MAILTO:user-commit...@lists.openstack.org
DESCRIPTION;LANGUAGE=en-US:\n\n\n  Meeting Conference Link: https://www
 .connectmeeting.att.com\n  Meeting Number: 8887160594\n  Code: 377
 3562\n  USA Toll-Free: 888-716-0594\n  USA Caller Paid: 215-861-61
 99\nFor Other Countries:Click Here to View Global Conference A
 ccess Numbers\n\n\n\nThe link to the wiki
  https://wiki.openstack.org/wiki/Fault_Genes_Working_Group\n\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TH;WKST=SU
EXDATE;TZID=Pacific Standard Time:20161124T08,20161208T08
SUMMARY;LANGUAGE=en-US:[Fault Genes] WG Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160519T08
DTEND;TZID=Pacific Standard Time:20160519T09
UID:04008200E00074C5B7101A82E00850B72A929FAAD101000
 0100028E111C3B604D445920643DCDC32B7B2
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170302T184338Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:114
LOCATION;LANGUAGE=en-US:Conference Call
X-MICROSOFT-CDO-APPT-SEQUENCE:114
X-MICROSOFT-CDO-OWNERAPPTID:1315723232
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:[Fault Genes] WG Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161103T08
DTEND;TZID=Pacific Standard Time:20161103T09
UID:04008200E00074C5B7101A82E00850B72A929FAAD101000
 0100028E111C3B604D445920643DCDC32B7B2
RECURRENCE-ID;TZID=Pacific Standard Time:20161103T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170302T184338Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:114
LOCATION:Conference Call
X-MICROSOFT-CDO-APPT-SEQUENCE:114
X-MICROSOFT-CDO-OWNERAPPTID:1315723232
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:[Fault Genes] WG Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161110T08
DTEND;TZID=Pacific Standard Time:20161110T09
UID:04008200E00074C5B7101A82E00850B72A929FAAD101000
 0100028E111C3B604D445920643DCDC32B7B2
RECURRENCE-ID;TZID=Pacific Standard Time:20161110T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170302T184338Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:114
LOCATION:Conference Call
X-MICROSOFT-CDO-APPT-SEQUENCE:114
X-MICROSOFT-CDO-OWNERAPPTID:1315723232
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:[Fault Genes] WG Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161201T08
DTEND;TZID=Pacific Standard Time:20161201T09
UID:04008200E00074C5B7101A82E00850B72A929FAAD101000
 0100028E111C3B604D445920643DCDC32B7B2
RECURRENCE-ID;TZID=Pacific Standard Time:20161201T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170302T184338Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:114
LOCATION:Conference Call
X-MICROSOFT-CDO-APPT-SEQUENCE:114
X-MICROSOFT-CDO-OWNERAPPTID:1315723232
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:[Fault Genes] WG Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161222T08
DTEND;TZID=Pacific Standard Time:20161222T09
UID:04008200E00074C5B7101A82E00850B72A929FAAD101000
 0100028E111C3B604D445920643DCDC32B7B2
RECURRENCE-ID;TZID=Pacific Standard Time:20161222T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170302T184338Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:114
LOCATION:Conference Call
X-MICROSOFT-CDO-APPT-SEQUENCE:114
X-MICROSOFT-CDO-OWNERAPPTID:1315723232
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-M

[Openstack-operators] [Fault Genes] WG Weekly Meeting

2017-03-02 Thread Nematollah Bidokhti

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Nematollah Bidokhti:MAILTO:nematollah.bidok...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='openstack
 -operat...@lists.openstack.org':MAILTO:openstack-operators@lists.openstack
 .org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='user-comm
 it...@lists.openstack.org':MAILTO:user-commit...@lists.openstack.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Jiri Such
 omel':MAILTO:jiri.sucho...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Andrew Ve
 itch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Alan McNa
 mee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Calum Lou
 don':MAILTO:calum.lou...@metaswitch.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Christoph
 er Price':MAILTO:christopher.pr...@ericsson.com
DESCRIPTION;LANGUAGE=en-US:Standard Agenda Items:\n-   Launchpad data t
 ransformation to Fault Genes database\n-   Stackoverflow data capture\
 n-   User Interface for Operators\n-   Machine learning analysis p
 rocess\n-   Collaboration with other projects such as Congress\n- 
   Open items\n\n\n\n  Meeting Conference Link: https://www.connectmeet
 ing.att.com\n  Meeting Number: 8887160594\n  Code: 3773562\n  
 USA Toll-Free: 888-716-0594\n  USA Caller Paid: 215-861-6199\nFor Othe
 r Countries:Click Here to View Global Conference Access Number
 s\n\n\n\nThe link to the wiki https://wik
 i.openstack.org/wiki/Fault_Genes_Working_Group\n\n\n\n
SUMMARY;LANGUAGE=en-US:[Fault Genes] WG Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20191212T08
DTEND;TZID=Pacific Standard Time:20191212T09
UID:04008200E00074C5B7101A82E00850B72A929FAAD101000
 0100028E111C3B604D445920643DCDC32B7B2
RECURRENCE-ID;TZID=Pacific Standard Time:20191212T08
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170302T184340Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:115
LOCATION;LANGUAGE=en-US:Conference Call
X-MICROSOFT-CDO-APPT-SEQUENCE:115
X-MICROSOFT-CDO-OWNERAPPTID:1315723232
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [openstack-dev] [keystone][defcore][refstack] Removal of the v2.0 API

2017-03-02 Thread Mark Voelker



> On Mar 1, 2017, at 6:01 PM, Rodrigo Duarte  wrote:
> 
> On Wed, Mar 1, 2017 at 7:10 PM, Lance Bragstad  wrote:
> During the PTG, Morgan mentioned that there was the possibility of keystone 
> removing the v2.0 API [0]. This thread is a follow up from that discussion to 
> make sure we loop in the right people and do everything by the books.
> 
> The result of the session [1] listed the following work items: 
> - Figure out how we can test the removal and make the job voting (does the 
> v3-only job count for this)?
> 
> We have two v3-only jobs, one only runs keystone's tempest plugin tests - 
> which are specific to federation (it configures a federated environment using 
> mod_shib) - and another one (non-voting) that runs tempest, I believe the 
> later can be a good way to initially validate the v2.0 removal.
>  
> - Reach out to defcore and refstack communities about removing v2.0 (which is 
> partially what this thread is doing)

Yup, we actually talked a bit about this in the past couple of weeks.  I’ve 
CC'd Luz who is playing point on capabilities scoring for the 2017.08 Guideline 
for Identity to make extra sure she’s aware. =)

At Your Service,

Mark T. Voelker
InteropWG Co-chair

> 
> Outside of this thread, what else do we have to do from a defcore perspective 
> to make this happen?
> 
> Thanks for the time!
> 
> [0] https://review.openstack.org/#/c/437667/
> [1] https://etherpad.openstack.org/p/pike-ptg-keystone-deprecations
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> -- 
> Rodrigo Duarte Sousa
> Senior Quality Engineer @ Red Hat
> MSc in Computer Science
> http://rodrigods.com
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

Re: [Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Grant Morley


Hi Saverio,

I have managed to fix it, turns out it was a HAPROXY issue and it wasn't 
terminating the backend connection correctly. The glance error logs sent 
me in the wrong direction.


Thank you for all of your suggestions to try and debug the issue.

Regards,


On 02/03/17 16:19, Grant Morley wrote:


If I use the image name I get the same result:

openstack image show Ubuntu-16.04
+--+--+
| Field| Value |
+--+--+
| checksum | 6008d3fdf650658965b132b547416d83 |
| container_format | bare |
| created_at   | 2016-12-07T16:00:54Z |
| disk_format  | raw |
| file | 
/v2/images/d5d43ba0-82e9-43de-8883-5ebaf07bf3e3/file |

| id   | d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 |
| min_disk | 0 |
| min_ram  | 0 |
| name | Ubuntu-16.04 |
| owner| 4a6213a64312482896130efc3047195c |
| properties   | 
direct_url='rbd://742cd163-32ac-4121-8060-d440aa7345d6/images/d5d43ba0-82e9-43de-8883-5ebaf07bf3e3/snap' 
|

| protected| False |
| schema   | /v2/schemas/image |
| size | 2361393152 |
| status   | active |
| tags | |
| updated_at   | 2016-12-07T16:01:45Z |
| virtual_size | None |
| visibility   | public |
+--+--+

Also there is only one entry in the DB for that image:

select * from images where name="Ubuntu-16.04";
+--+--+++---+-+-++-+-+--+--+--+--+-+---+--+
| id   | name | size   | 
status | is_public | created_at  | updated_at  | 
deleted_at | deleted | disk_format | container_format | 
checksum | owner| 
min_disk | min_ram | protected | virtual_size |

+--+--+++---+-+-++-+-+--+--+--+--+-+---+--+
| d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04 | 2361393152 | 
active | 1 | 2016-12-07 16:00:54 | 2016-12-07 16:01:45 | 
NULL   |   0 | raw | bare | 
6008d3fdf650658965b132b547416d83 | 4a6213a64312482896130efc3047195c 
|0 |   0 | 0 | NULL |

+--+--+++---+-+-++-+-+--+--+--+--+-+---+--+

Regards,

On 02/03/17 16:08, Saverio Proto wrote:

select * from images where name=''Ubuntu-16.04";


--
Grant Morley
Cloud Lead
Absolute DevOps Ltd
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
www.absolutedevops.io  
gr...@absolutedevops.io  0845 874 0580


--
Grant Morley
Cloud Lead
Absolute DevOps Ltd
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
www.absolutedevops.io  
gr...@absolutedevops.io  0845 874 0580
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Grant Morley


If I use the image name I get the same result:

openstack image show Ubuntu-16.04
+--+--+
| Field| Value |
+--+--+
| checksum | 6008d3fdf650658965b132b547416d83 |
| container_format | bare |
| created_at   | 2016-12-07T16:00:54Z |
| disk_format  | raw |
| file | /v2/images/d5d43ba0-82e9-43de-8883-5ebaf07bf3e3/file |
| id   | d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 |
| min_disk | 0 |
| min_ram  | 0 |
| name | Ubuntu-16.04 |
| owner| 4a6213a64312482896130efc3047195c |
| properties   | 
direct_url='rbd://742cd163-32ac-4121-8060-d440aa7345d6/images/d5d43ba0-82e9-43de-8883-5ebaf07bf3e3/snap' 
|

| protected| False |
| schema   | /v2/schemas/image |
| size | 2361393152 |
| status   | active |
| tags | |
| updated_at   | 2016-12-07T16:01:45Z |
| virtual_size | None |
| visibility   | public |
+--+--+

Also there is only one entry in the DB for that image:

select * from images where name="Ubuntu-16.04";
+--+--+++---+-+-++-+-+--+--+--+--+-+---+--+
| id   | name | size | status | 
is_public | created_at  | updated_at  | deleted_at | 
deleted | disk_format | container_format | 
checksum | owner| 
min_disk | min_ram | protected | virtual_size |

+--+--+++---+-+-++-+-+--+--+--+--+-+---+--+
| d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04 | 2361393152 | 
active | 1 | 2016-12-07 16:00:54 | 2016-12-07 16:01:45 | 
NULL   |   0 | raw | bare | 
6008d3fdf650658965b132b547416d83 | 4a6213a64312482896130efc3047195c 
|0 |   0 | 0 | NULL |

+--+--+++---+-+-++-+-+--+--+--+--+-+---+--+

Regards,

On 02/03/17 16:08, Saverio Proto wrote:

select * from images where name=''Ubuntu-16.04";


--
Grant Morley
Cloud Lead
Absolute DevOps Ltd
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
www.absolutedevops.io  
gr...@absolutedevops.io  0845 874 0580
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Saverio Proto

Everything LTGM

but if you do:

openstack image show Ubuntu-16.04

then you get again the error about the multiple names ?

if you go to the glance database and you do:

select * from images where name=''Ubuntu-16.04";

how many rows you have ?

after we collect this information we can try to understand if this is nova
or glance bug.

thank you

Saverio


2017-03-02 17:01 GMT+01:00 Grant Morley :

> sure no problem:
>
> openstack image show d5d43ba0-82e9-43de-8883-5ebaf07bf3e3
> +--+
> --+
> | Field| Value
>
> |
> +--+
> --+
> | checksum | 6008d3fdf650658965b132b547416d
> 83
> |
> | container_format | bare
>
> |
> | created_at   | 2016-12-07T16:00:54Z
>
> |
> | disk_format  | raw
>
> |
> | file | /v2/images/d5d43ba0-82e9-43de-
> 8883-5ebaf07bf3e3/file
> |
> | id   | d5d43ba0-82e9-43de-8883-
> 5ebaf07bf3e3
> |
> | min_disk | 0
>
> |
> | min_ram  | 0
>
> |
> | name | Ubuntu-16.04
>
> |
> | owner| 4a6213a64312482896130efc304719
> 5c
> |
> | properties   | direct_url='rbd://742cd163-
> 32ac-4121-8060-d440aa7345d6/images/d5d43ba0-82e9-43de-8883-5ebaf07bf3e3/snap'
> |
> | protected| False
>
> |
> | schema   | /v2/schemas/image
>
> |
> | size | 2361393152
>
> |
> | status   | active
>
> |
> | tags |
>
> |
> | updated_at   | 2016-12-07T16:01:45Z
>
> |
> | virtual_size | None
>
> |
> | visibility   | public
>
> |
> +--+
> --+
>
> On 02/03/17 15:56, Saverio Proto wrote:
>
> Can you share with us the output of:
>
> openstack image show 
>
> for that image ?
>
> Saverio
>
>
> 2017-03-02 13:54 GMT+01:00 Grant Morley :
>
>> Unfortunately not, I still get the same error.
>>
>> Grant
>>
>> On 02/03/17 12:54, Saverio Proto wrote:
>>
>> If you pass the uuid of the image does it work ?
>>
>> Saverio
>>
>> 2017-03-02 13:49 GMT+01:00 Grant Morley :
>>
>>> Hi Saverio,
>>>
>>> We are running Mitaka - sorry forgot to mention that.
>>>
>>> Grant
>>>
>>> On 02/03/17 12:45, Saverio Proto wrote:
>>>
>>> What version of Openstack are we talking about ?
>>>
>>> Saverio
>>>
>>> 2017-03-02 12:11 GMT+01:00 Grant Morley :
>>>
 Hi All,

 Not sure if anyone can help, but as of today we are unable to launch
 any instances and I have traced back the error to glance. Whenever I try
 and launch an instance I get the below returned:

 openstack server create --flavor g1.small --image "Ubuntu-16.04"
 --key-name ib-desktop --security-group default --nic
 net-id=e2d925f0-63c1-442f-9158-6a138e5847ce gmtest
 Could not find resource Ubuntu-16.04

 The image exists:

 openstack image list | grep Ubuntu-16.04

 | d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04   | active |

 The traceback gives a really odd message about Multiple choices ( All
 images have unique names )

 Below is the stack trace - not sure if anyone has come across this
 before? I am stumped at the moment.

 2017-03-02 11:10:16.842 2107 INFO eventlet.wsgi.server [-]
 10.6.2.255,10.6.0.39 - - [02/Mar/2017 11:10:16] "GET
 /images/detail?is_public=none&limit=20 HTTP/1.1" 300 787 0.000769
 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
 [req-3b498a7e-2d6a-4337-a314-12abfbac0117
 4c91f07132454a97b21fff35402b7825 4a6213a64312482896130efc3047195c - -
 -] Registry client request GET /images/detail raised MultipleChoices
 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
 Traceback (most recent call last):
 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
 File "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/
 glance/registry/client/v1/client.py", line 123, in do_request
 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
 **kwargs)
 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
 File 
 "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
 line 70, in wrapped
 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
 return func(self, *args, **kwargs)
 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
 File 
 "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
 line 373, in do_request
 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
 headers=copy.deepcopy(headers))
 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
 File 
 "/openstack/venvs/

Re: [Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Grant Morley


sure no problem:

openstack image show d5d43ba0-82e9-43de-8883-5ebaf07bf3e3
+--+--+
| Field| Value |
+--+--+
| checksum | 6008d3fdf650658965b132b547416d83 |
| container_format | bare |
| created_at   | 2016-12-07T16:00:54Z |
| disk_format  | raw |
| file | /v2/images/d5d43ba0-82e9-43de-8883-5ebaf07bf3e3/file |
| id   | d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 |
| min_disk | 0 |
| min_ram  | 0 |
| name | Ubuntu-16.04 |
| owner| 4a6213a64312482896130efc3047195c |
| properties   | 
direct_url='rbd://742cd163-32ac-4121-8060-d440aa7345d6/images/d5d43ba0-82e9-43de-8883-5ebaf07bf3e3/snap' 
|

| protected| False |
| schema   | /v2/schemas/image |
| size | 2361393152 |
| status   | active |
| tags | |
| updated_at   | 2016-12-07T16:01:45Z |
| virtual_size | None |
| visibility   | public |
+--+--+


On 02/03/17 15:56, Saverio Proto wrote:

Can you share with us the output of:

openstack image show 

for that image ?

Saverio


2017-03-02 13:54 GMT+01:00 Grant Morley >:


Unfortunately not, I still get the same error.

Grant


On 02/03/17 12:54, Saverio Proto wrote:

If you pass the uuid of the image does it work ?

Saverio

2017-03-02 13:49 GMT+01:00 Grant Morley mailto:gr...@absolutedevops.io>>:

Hi Saverio,

We are running Mitaka - sorry forgot to mention that.

Grant


On 02/03/17 12:45, Saverio Proto wrote:

What version of Openstack are we talking about ?

Saverio

2017-03-02 12:11 GMT+01:00 Grant Morley
mailto:gr...@absolutedevops.io>>:

Hi All,

Not sure if anyone can help, but as of today we are
unable to launch any instances and I have traced back
the error to glance. Whenever I try and launch an
instance I get the below returned:

openstack server create --flavor g1.small --image
"Ubuntu-16.04" --key-name ib-desktop --security-group
default --nic
net-id=e2d925f0-63c1-442f-9158-6a138e5847ce gmtest
Could not find resource Ubuntu-16.04

The image exists:

openstack image list | grep Ubuntu-16.04

| d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04  
| active |


The traceback gives a really odd message about Multiple
choices ( All images have unique names )

Below is the stack trace - not sure if anyone has come
across this before? I am stumped at the moment.

2017-03-02 11:10:16.842 2107 INFO eventlet.wsgi.server
[-] 10.6.2.255,10.6.0.39 - - [02/Mar/2017 11:10:16] "GET
/images/detail?is_public=none&limit=20 HTTP/1.1" 300 787
0.000769
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client
[req-3b498a7e-2d6a-4337-a314-12abfbac0117
4c91f07132454a97b21fff35402b7825
4a6213a64312482896130efc3047195c - - -] Registry client
request GET /images/detail raised MultipleChoices
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client Traceback (most recent
call last):
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/registry/client/v1/client.py",
line 123, in do_request
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client **kwargs)
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 70, in wrapped
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client return func(self,
*args, **kwargs)
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 373, in do_request
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client
headers=copy.deepcopy(headers))
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",

Re: [Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Saverio Proto

Can you share with us the output of:

openstack image show 

for that image ?

Saverio


2017-03-02 13:54 GMT+01:00 Grant Morley :

> Unfortunately not, I still get the same error.
>
> Grant
>
> On 02/03/17 12:54, Saverio Proto wrote:
>
> If you pass the uuid of the image does it work ?
>
> Saverio
>
> 2017-03-02 13:49 GMT+01:00 Grant Morley :
>
>> Hi Saverio,
>>
>> We are running Mitaka - sorry forgot to mention that.
>>
>> Grant
>>
>> On 02/03/17 12:45, Saverio Proto wrote:
>>
>> What version of Openstack are we talking about ?
>>
>> Saverio
>>
>> 2017-03-02 12:11 GMT+01:00 Grant Morley :
>>
>>> Hi All,
>>>
>>> Not sure if anyone can help, but as of today we are unable to launch any
>>> instances and I have traced back the error to glance. Whenever I try and
>>> launch an instance I get the below returned:
>>>
>>> openstack server create --flavor g1.small --image "Ubuntu-16.04"
>>> --key-name ib-desktop --security-group default --nic
>>> net-id=e2d925f0-63c1-442f-9158-6a138e5847ce gmtest
>>> Could not find resource Ubuntu-16.04
>>>
>>> The image exists:
>>>
>>> openstack image list | grep Ubuntu-16.04
>>>
>>> | d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04   | active |
>>>
>>> The traceback gives a really odd message about Multiple choices ( All
>>> images have unique names )
>>>
>>> Below is the stack trace - not sure if anyone has come across this
>>> before? I am stumped at the moment.
>>>
>>> 2017-03-02 11:10:16.842 2107 INFO eventlet.wsgi.server [-]
>>> 10.6.2.255,10.6.0.39 - - [02/Mar/2017 11:10:16] "GET
>>> /images/detail?is_public=none&limit=20 HTTP/1.1" 300 787 0.000769
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> [req-3b498a7e-2d6a-4337-a314-12abfbac0117 4c91f07132454a97b21fff35402b7825
>>> 4a6213a64312482896130efc3047195c - - -] Registry client request GET
>>> /images/detail raised MultipleChoices
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> Traceback (most recent call last):
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> File "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/
>>> glance/registry/client/v1/client.py", line 123, in do_request
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> **kwargs)
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> File 
>>> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
>>> line 70, in wrapped
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> return func(self, *args, **kwargs)
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> File 
>>> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
>>> line 373, in do_request
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> headers=copy.deepcopy(headers))
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> File 
>>> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
>>> line 87, in wrapped
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> return func(self, method, url, body, headers)
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> File 
>>> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
>>> line 534, in _do_request
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> raise exception.MultipleChoices(body=read_body(res))
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> MultipleChoices: The request returned a 302 Multiple Choices. This
>>> generally means that you have not included a version indicator in a request
>>> URI.
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client The
>>> body of response returned:
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> {"versions": [{"status": "CURRENT", "id": "v2.3", "links": [{"href":
>>> "http://10.6.0.3:9191/v2/"; , "rel":
>>> "self"}]}, {"status": "SUPPORTED", "id": "v2.2", "links": [{"href":
>>> "http://10.6.0.3:9191/v2/"; , "rel":
>>> "self"}]}, {"status": "SUPPORTED", "id": "v2.1", "links": [{"href":
>>> "http://10.6.0.3:9191/v2/"; , "rel":
>>> "self"}]}, {"status": "SUPPORTED", "id": "v2.0", "links": [{"href":
>>> "http://10.6.0.3:9191/v2/"; , "rel":
>>> "self"}]}, {"status": "SUPPORTED", "id": "v1.1", "links": [{"href":
>>> "http://10.6.0.3:9191/v1/"; , "rel":
>>> "self"}]}, {"status": "SUPPORTED", "id": "v1.0", "links": [{"href":
>>> "http://10.6.0.3:9191/v1/"; , "rel":
>>> "self"}]}]}
>>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>>> 2017-03-02 11:10:16.844 2104 ERROR glance.

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

2017-03-02 Thread Andy McCrae

Hi Amit,

Sending it again to include the ML!

On 2 March 2017 at 11:01, Amit Kumar  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

2017-03-02 Thread 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"  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 
> *Date: *Thursday, March 2, 2017 at 11:01 AM
> *To: *Openstack , 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

Re: [Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Grant Morley


Unfortunately not, I still get the same error.

Grant


On 02/03/17 12:54, Saverio Proto wrote:

If you pass the uuid of the image does it work ?

Saverio

2017-03-02 13:49 GMT+01:00 Grant Morley >:


Hi Saverio,

We are running Mitaka - sorry forgot to mention that.

Grant


On 02/03/17 12:45, Saverio Proto wrote:

What version of Openstack are we talking about ?

Saverio

2017-03-02 12:11 GMT+01:00 Grant Morley mailto:gr...@absolutedevops.io>>:

Hi All,

Not sure if anyone can help, but as of today we are unable to
launch any instances and I have traced back the error to
glance. Whenever I try and launch an instance I get the below
returned:

openstack server create --flavor g1.small --image
"Ubuntu-16.04" --key-name ib-desktop --security-group default
--nic net-id=e2d925f0-63c1-442f-9158-6a138e5847ce gmtest
Could not find resource Ubuntu-16.04

The image exists:

openstack image list | grep Ubuntu-16.04

| d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04   |
active |

The traceback gives a really odd message about Multiple
choices ( All images have unique names )

Below is the stack trace - not sure if anyone has come across
this before? I am stumped at the moment.

2017-03-02 11:10:16.842 2107 INFO eventlet.wsgi.server [-]
10.6.2.255,10.6.0.39 - - [02/Mar/2017 11:10:16] "GET
/images/detail?is_public=none&limit=20 HTTP/1.1" 300 787 0.000769
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client
[req-3b498a7e-2d6a-4337-a314-12abfbac0117
4c91f07132454a97b21fff35402b7825
4a6213a64312482896130efc3047195c - - -] Registry client
request GET /images/detail raised MultipleChoices
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client Traceback (most recent call
last):
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/registry/client/v1/client.py",
line 123, in do_request
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client **kwargs)
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 70, in wrapped
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client return func(self, *args,
**kwargs)
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 373, in do_request
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client headers=copy.deepcopy(headers))
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 87, in wrapped
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client return func(self, method,
url, body, headers)
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 534, in _do_request
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client raise
exception.MultipleChoices(body=read_body(res))
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client MultipleChoices: The request
returned a 302 Multiple Choices. This generally means that
you have not included a version indicator in a request URI.
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client The body of response returned:
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client {"versions": [{"status":
"CURRENT", "id": "v2.3", "links": [{"href":
"http://10.6.0.3:9191/v2/"; , "rel":
"self"}]}, {"status": "SUPPORTED", "id": "v2.2", "links":
[{"href": "http://10.6.0.3:9191/v2/";
, "rel": "self"}]}, {"status":
"SUPPORTED", "id": "v2.1", "links": [{"href":
"http://10.6.0.3:9191/v2/"; , "rel":
"self"}]}, {"status": "SUPPORTED", "id": "v2.0", "links":
[{"href": "http://10.6.0.3:9191/v2/";
, "rel": "self"}]}, {"status":
"SUPPORTED", "id": "v1.1", "links": [{"href":
"http://10.6.0.3:9191/v1/"; , "rel

Re: [Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Saverio Proto

If you pass the uuid of the image does it work ?

Saverio

2017-03-02 13:49 GMT+01:00 Grant Morley :

> Hi Saverio,
>
> We are running Mitaka - sorry forgot to mention that.
>
> Grant
>
> On 02/03/17 12:45, Saverio Proto wrote:
>
> What version of Openstack are we talking about ?
>
> Saverio
>
> 2017-03-02 12:11 GMT+01:00 Grant Morley :
>
>> Hi All,
>>
>> Not sure if anyone can help, but as of today we are unable to launch any
>> instances and I have traced back the error to glance. Whenever I try and
>> launch an instance I get the below returned:
>>
>> openstack server create --flavor g1.small --image "Ubuntu-16.04"
>> --key-name ib-desktop --security-group default --nic
>> net-id=e2d925f0-63c1-442f-9158-6a138e5847ce gmtest
>> Could not find resource Ubuntu-16.04
>>
>> The image exists:
>>
>> openstack image list | grep Ubuntu-16.04
>>
>> | d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04   | active |
>>
>> The traceback gives a really odd message about Multiple choices ( All
>> images have unique names )
>>
>> Below is the stack trace - not sure if anyone has come across this
>> before? I am stumped at the moment.
>>
>> 2017-03-02 11:10:16.842 2107 INFO eventlet.wsgi.server [-]
>> 10.6.2.255,10.6.0.39 - - [02/Mar/2017 11:10:16] "GET
>> /images/detail?is_public=none&limit=20 HTTP/1.1" 300 787 0.000769
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> [req-3b498a7e-2d6a-4337-a314-12abfbac0117 4c91f07132454a97b21fff35402b7825
>> 4a6213a64312482896130efc3047195c - - -] Registry client request GET
>> /images/detail raised MultipleChoices
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> Traceback (most recent call last):
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> File "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/
>> glance/registry/client/v1/client.py", line 123, in do_request
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> **kwargs)
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> File 
>> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
>> line 70, in wrapped
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> return func(self, *args, **kwargs)
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> File 
>> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
>> line 373, in do_request
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> headers=copy.deepcopy(headers))
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> File 
>> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
>> line 87, in wrapped
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> return func(self, method, url, body, headers)
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> File 
>> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
>> line 534, in _do_request
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> raise exception.MultipleChoices(body=read_body(res))
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> MultipleChoices: The request returned a 302 Multiple Choices. This
>> generally means that you have not included a version indicator in a request
>> URI.
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client The
>> body of response returned:
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> {"versions": [{"status": "CURRENT", "id": "v2.3", "links": [{"href":
>> "http://10.6.0.3:9191/v2/"; , "rel": "self"}]},
>> {"status": "SUPPORTED", "id": "v2.2", "links": [{"href":
>> "http://10.6.0.3:9191/v2/"; , "rel": "self"}]},
>> {"status": "SUPPORTED", "id": "v2.1", "links": [{"href":
>> "http://10.6.0.3:9191/v2/"; , "rel": "self"}]},
>> {"status": "SUPPORTED", "id": "v2.0", "links": [{"href":
>> "http://10.6.0.3:9191/v2/"; , "rel": "self"}]},
>> {"status": "SUPPORTED", "id": "v1.1", "links": [{"href":
>> "http://10.6.0.3:9191/v1/"; , "rel": "self"}]},
>> {"status": "SUPPORTED", "id": "v1.0", "links": [{"href":
>> "http://10.6.0.3:9191/v1/"; , "rel": "self"}]}]}
>> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
>> 2017-03-02 11:10:16.844 2104 ERROR glance.common.wsgi
>> [req-3b498a7e-2d6a-4337-a314-12abfbac0117 4c91f07132454a97b21fff35402b7825
>> 4a6213a64312482896130efc3047195c - - -] Caught error: The request
>> returned a 302 Multiple Choices. This generally means that you have not
>> included a version indicator in a request URI.
>>
>> Any help would be great.
>>
>> Regards,
>> --
>> Grant Mo

Re: [Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Grant Morley


Hi Saverio,

We are running Mitaka - sorry forgot to mention that.

Grant


On 02/03/17 12:45, Saverio Proto wrote:

What version of Openstack are we talking about ?

Saverio

2017-03-02 12:11 GMT+01:00 Grant Morley >:


Hi All,

Not sure if anyone can help, but as of today we are unable to
launch any instances and I have traced back the error to glance.
Whenever I try and launch an instance I get the below returned:

openstack server create --flavor g1.small --image "Ubuntu-16.04"
--key-name ib-desktop --security-group default --nic
net-id=e2d925f0-63c1-442f-9158-6a138e5847ce gmtest
Could not find resource Ubuntu-16.04

The image exists:

openstack image list | grep Ubuntu-16.04

| d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04   | active |

The traceback gives a really odd message about Multiple choices (
All images have unique names )

Below is the stack trace - not sure if anyone has come across this
before? I am stumped at the moment.

2017-03-02 11:10:16.842 2107 INFO eventlet.wsgi.server [-]
10.6.2.255,10.6.0.39 - - [02/Mar/2017 11:10:16] "GET
/images/detail?is_public=none&limit=20 HTTP/1.1" 300 787 0.000769
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client
[req-3b498a7e-2d6a-4337-a314-12abfbac0117
4c91f07132454a97b21fff35402b7825 4a6213a64312482896130efc3047195c
- - -] Registry client request GET /images/detail raised
MultipleChoices
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client Traceback (most recent call last):
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client   File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/registry/client/v1/client.py",
line 123, in do_request
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client **kwargs)
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client   File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 70, in wrapped
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client return func(self, *args,
**kwargs)
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client   File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 373, in do_request
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client headers=copy.deepcopy(headers))
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client   File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 87, in wrapped
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client return func(self, method,
url, body, headers)
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client   File

"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
line 534, in _do_request
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client raise
exception.MultipleChoices(body=read_body(res))
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client MultipleChoices: The request
returned a 302 Multiple Choices. This generally means that you
have not included a version indicator in a request URI.
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client The body of response returned:
2017-03-02 11:10:16.843 2104 ERROR
glance.registry.client.v1.client {"versions": [{"status":
"CURRENT", "id": "v2.3", "links": [{"href":
"http://10.6.0.3:9191/v2/"; , "rel":
"self"}]}, {"status": "SUPPORTED", "id": "v2.2", "links":
[{"href": "http://10.6.0.3:9191/v2/"; ,
"rel": "self"}]}, {"status": "SUPPORTED", "id": "v2.1", "links":
[{"href": "http://10.6.0.3:9191/v2/"; ,
"rel": "self"}]}, {"status": "SUPPORTED", "id": "v2.0", "links":
[{"href": "http://10.6.0.3:9191/v2/"; ,
"rel": "self"}]}, {"status": "SUPPORTED", "id": "v1.1", "links":
[{"href": "http://10.6.0.3:9191/v1/"; ,
"rel": "self"}]}, {"status": "SUPPORTED", "id": "v1.0", "links":
[{"href": "http://10.6.0.3:9191/v1/"; ,
"rel": "self"}]}]}
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
2017-03-02 11:10:16.844 2104 ERROR glance.common.wsgi
[req-3b498a7e-2d6a-4337-a314-12abfbac0117
4c91f07132454a97b21fff35402b7825 4a6213a64312482896130efc3047195c
- - -] Caught error: The request returned a 302 Multiple Choices.
This generally means that you have not included a version
indicator in a request URI.

Any help would be gr

Re: [Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Saverio Proto

What version of Openstack are we talking about ?

Saverio

2017-03-02 12:11 GMT+01:00 Grant Morley :

> Hi All,
>
> Not sure if anyone can help, but as of today we are unable to launch any
> instances and I have traced back the error to glance. Whenever I try and
> launch an instance I get the below returned:
>
> openstack server create --flavor g1.small --image "Ubuntu-16.04"
> --key-name ib-desktop --security-group default --nic
> net-id=e2d925f0-63c1-442f-9158-6a138e5847ce gmtest
> Could not find resource Ubuntu-16.04
>
> The image exists:
>
> openstack image list | grep Ubuntu-16.04
>
> | d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04   | active |
>
> The traceback gives a really odd message about Multiple choices ( All
> images have unique names )
>
> Below is the stack trace - not sure if anyone has come across this before?
> I am stumped at the moment.
>
> 2017-03-02 11:10:16.842 2107 INFO eventlet.wsgi.server [-]
> 10.6.2.255,10.6.0.39 - - [02/Mar/2017 11:10:16] "GET
> /images/detail?is_public=none&limit=20 HTTP/1.1" 300 787 0.000769
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> [req-3b498a7e-2d6a-4337-a314-12abfbac0117 4c91f07132454a97b21fff35402b7825
> 4a6213a64312482896130efc3047195c - - -] Registry client request GET
> /images/detail raised MultipleChoices
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> Traceback (most recent call last):
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> File "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/
> glance/registry/client/v1/client.py", line 123, in do_request
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> **kwargs)
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> File 
> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
> line 70, in wrapped
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> return func(self, *args, **kwargs)
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> File 
> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
> line 373, in do_request
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> headers=copy.deepcopy(headers))
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> File 
> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
> line 87, in wrapped
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> return func(self, method, url, body, headers)
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> File 
> "/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py",
> line 534, in _do_request
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> raise exception.MultipleChoices(body=read_body(res))
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> MultipleChoices: The request returned a 302 Multiple Choices. This
> generally means that you have not included a version indicator in a request
> URI.
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client The
> body of response returned:
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> {"versions": [{"status": "CURRENT", "id": "v2.3", "links": [{"href":
> "http://10.6.0.3:9191/v2/"; , "rel": "self"}]},
> {"status": "SUPPORTED", "id": "v2.2", "links": [{"href":
> "http://10.6.0.3:9191/v2/"; , "rel": "self"}]},
> {"status": "SUPPORTED", "id": "v2.1", "links": [{"href":
> "http://10.6.0.3:9191/v2/"; , "rel": "self"}]},
> {"status": "SUPPORTED", "id": "v2.0", "links": [{"href":
> "http://10.6.0.3:9191/v2/"; , "rel": "self"}]},
> {"status": "SUPPORTED", "id": "v1.1", "links": [{"href":
> "http://10.6.0.3:9191/v1/"; , "rel": "self"}]},
> {"status": "SUPPORTED", "id": "v1.0", "links": [{"href":
> "http://10.6.0.3:9191/v1/"; , "rel": "self"}]}]}
> 2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
> 2017-03-02 11:10:16.844 2104 ERROR glance.common.wsgi
> [req-3b498a7e-2d6a-4337-a314-12abfbac0117 4c91f07132454a97b21fff35402b7825
> 4a6213a64312482896130efc3047195c - - -] Caught error: The request
> returned a 302 Multiple Choices. This generally means that you have not
> included a version indicator in a request URI.
>
> Any help would be great.
>
> Regards,
> --
> Grant Morley
> Cloud Lead
> Absolute DevOps Ltd
> Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
> www.absolutedevops.io gr...@absolutedevops.io  0845
> 874 0580
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.or

[Openstack-operators] Unable to launch instances because of glance errors

2017-03-02 Thread Grant Morley


Hi All,

Not sure if anyone can help, but as of today we are unable to launch any 
instances and I have traced back the error to glance. Whenever I try and 
launch an instance I get the below returned:


openstack server create --flavor g1.small --image "Ubuntu-16.04" 
--key-name ib-desktop --security-group default --nic 
net-id=e2d925f0-63c1-442f-9158-6a138e5847ce gmtest

Could not find resource Ubuntu-16.04

The image exists:

openstack image list | grep Ubuntu-16.04

| d5d43ba0-82e9-43de-8883-5ebaf07bf3e3 | Ubuntu-16.04   | active |

The traceback gives a really odd message about Multiple choices ( All 
images have unique names )


Below is the stack trace - not sure if anyone has come across this 
before? I am stumped at the moment.


2017-03-02 11:10:16.842 2107 INFO eventlet.wsgi.server [-] 
10.6.2.255,10.6.0.39 - - [02/Mar/2017 11:10:16] "GET 
/images/detail?is_public=none&limit=20 HTTP/1.1" 300 787 0.000769
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client 
[req-3b498a7e-2d6a-4337-a314-12abfbac0117 
4c91f07132454a97b21fff35402b7825 4a6213a64312482896130efc3047195c - - -] 
Registry client request GET /images/detail raised MultipleChoices
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client 
Traceback (most recent call last):
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client   
File 
"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/registry/client/v1/client.py", 
line 123, in do_request
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client 
**kwargs)
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client   
File 
"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py", 
line 70, in wrapped
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client 
return func(self, *args, **kwargs)
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client   
File 
"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py", 
line 373, in do_request
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client 
headers=copy.deepcopy(headers))
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client   
File 
"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py", 
line 87, in wrapped
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client 
return func(self, method, url, body, headers)
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client   
File 
"/openstack/venvs/glance-13.3.8/lib/python2.7/site-packages/glance/common/client.py", 
line 534, in _do_request
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client 
raise exception.MultipleChoices(body=read_body(res))
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client 
MultipleChoices: The request returned a 302 Multiple Choices. This 
generally means that you have not included a version indicator in a 
request URI.

2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client The 
body of response returned:
2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client 
{"versions": [{"status": "CURRENT", "id": "v2.3", "links": [{"href": 
"http://10.6.0.3:9191/v2/";, "rel": "self"}]}, {"status": "SUPPORTED", 
"id": "v2.2", "links": [{"href": "http://10.6.0.3:9191/v2/";, "rel": 
"self"}]}, {"status": "SUPPORTED", "id": "v2.1", "links": [{"href": 
"http://10.6.0.3:9191/v2/";, "rel": "self"}]}, {"status": "SUPPORTED", 
"id": "v2.0", "links": [{"href": "http://10.6.0.3:9191/v2/";, "rel": 
"self"}]}, {"status": "SUPPORTED", "id": "v1.1", "links": [{"href": 
"http://10.6.0.3:9191/v1/";, "rel": "self"}]}, {"status": "SUPPORTED", 
"id": "v1.0", "links": [{"href": "http://10.6.0.3:9191/v1/";, "rel": 
"self"}]}]}

2017-03-02 11:10:16.843 2104 ERROR glance.registry.client.v1.client
2017-03-02 11:10:16.844 2104 ERROR glance.common.wsgi 
[req-3b498a7e-2d6a-4337-a314-12abfbac0117 
4c91f07132454a97b21fff35402b7825 4a6213a64312482896130efc3047195c - - -] 
Caught error: The request returned a 302 Multiple Choices. This 
generally means that you have not included a version indicator in a 
request URI.


Any help would be great.

Regards,

--
Grant Morley
Cloud Lead
Absolute DevOps Ltd
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
www.absolutedevops.io  
gr...@absolutedevops.io  0845 874 0580
___
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

2017-03-02 Thread Alexandra Settle

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 
Date: Thursday, March 2, 2017 at 11:01 AM
To: Openstack , OpenStack Operators 

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

2017-03-02 Thread 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

[Openstack-operators] Upcoming Ops Midcycle

Re: [Openstack-operators] Operators Mid-cycle Moderator

Re: [Openstack-operators] Operators Mid-cycle Moderator

Re: [Openstack-operators] Operators Mid-cycle Moderator

[Openstack-operators] Fwd: [openstack-dev] [tc][swg][all] Leadership training sign-up is open!

Re: [Openstack-operators] Forum Brainstorming???

Re: [Openstack-operators] (openstack-ansible) Mitaka 13.3.12 failing to report correct resource usage

[Openstack-operators] (openstack-ansible) Mitaka 13.3.12 failing to report correct resource usage

[Openstack-operators] [Fault Genes] WG Weekly Meeting

[Openstack-operators] [Fault Genes] WG Weekly Meeting

[Openstack-operators] [Fault Genes] WG Weekly Meeting

Re: [Openstack-operators] [openstack-dev] [keystone][defcore][refstack] Removal of the v2.0 API

Re: [Openstack-operators] Unable to launch instances because of glance errors

Re: [Openstack-operators] Unable to launch instances because of glance errors

Re: [Openstack-operators] Unable to launch instances because of glance errors

Re: [Openstack-operators] Unable to launch instances because of glance errors

Re: [Openstack-operators] Unable to launch instances because of glance errors

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

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

Re: [Openstack-operators] Unable to launch instances because of glance errors

Re: [Openstack-operators] Unable to launch instances because of glance errors

Re: [Openstack-operators] Unable to launch instances because of glance errors

Re: [Openstack-operators] Unable to launch instances because of glance errors

[Openstack-operators] Unable to launch instances because of glance errors

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

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

26 matches

Site Navigation

Mail list logo

Footer information