Open Stack

Hi Team,

I have installed kilo on Ubuntu 14.04. Everything was working fine but suddenly, I am getting an error in glance image-list.

Before installing mongodb, it was working fine. But now, it is not.

root at kilocontroller:/home/oss# glance image-list
None is not of type u'string'

Failed validating u'type' in schema[u'properties'][u'ramdisk_id']:
    {u'description': u'ID of image stored in Glance that should be used as the ramdisk when booting an AMI-style image.',
     u'is_base': False,
     u'pattern': u'^([0-9a-fA-F]){8}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-9a-fA-F]){12}$',
     u'type': u'string'}

On instance[u'ramdisk_id']:
    None

I have checked the google but not able to find the resolution for it.

Could you let me know what I'm doing wrong.

Kind thoughts,
Bhumika Jain





-----Original Message-----
From: openstack-operators-request at lists.openstack.org [mailto:openstack-operators-request at lists.openstack.org]
Sent: Thursday, May 21, 2015 5:30 PM
To: openstack-operators at lists.openstack.org
Subject: OpenStack-operators Digest, Vol 55, Issue 23

Send OpenStack-operators mailing list submissions to
        openstack-operators at lists.openstack.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

or, via email, send a message with subject or body 'help' to
        openstack-operators-request at lists.openstack.org

You can reach the person managing the list at
        openstack-operators-owner at lists.openstack.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of OpenStack-operators digest..."


Today's Topics:

   1. Tracing requests across services in the logs (Simon Pasquier)
   2. Re: Introducing the Ops Tags Team (Jesus M. Gonzalez-Barahona)
   3. [App-Catalog] Planning/working session    Wednesday in Vancouver
      (Christopher Aedo)
   4. [Large Deployments Team]  Today's sessions (Matt Van Winkle)
   5. [glance] [kolla] [magnum] [nova] [neutron] Vancouver Summit
      Operations Containers Session (Richard Raseley)
   6. Re: [openstack-dev] [glance] [kolla] [magnum] [nova]
      [neutron] Vancouver Summit Operations Containers Session
      (Daniel Comnea)


----------------------------------------------------------------------

Message: 1
Date: Wed, 20 May 2015 05:39:57 -0700
From: Simon Pasquier <spasquier at mirantis.com>
To: "openstack-operators at lists.openstack.org"
        <openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] Tracing requests across services in the
        logs
Message-ID:
        <CAOq3GZVqTR69freOcRr+TVt2LdNsvNn33=vS=fTSzOWD=rrfVw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,
During the ops session on logging [0], we discussed how to correlate between request ids when a request crosses service boundaries.
I'd encourage everybody interested by this effort to look at the proposed specifications [1] [2] and provide feedback. One of the questions raised is whether it makes sense to have a unique request id or different request ids per service with a way to map them together.
BR,
Simon

[0] https://etherpad.openstack.org/p/YVR-ops-logging
[1] https://review.openstack.org/#/c/156508/
[2] https://review.openstack.org/#/c/164582/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150520/a1b1e80a/attachment-0001.html>

------------------------------

Message: 2
Date: Wed, 20 May 2015 14:51:17 +0200
From: "Jesus M. Gonzalez-Barahona" <jgb at bitergia.com>
To: Tom Fifield <tom at openstack.org>
Cc: OpenStack Operators <openstack-operators at lists.openstack.org>
Subject: Re: [Openstack-operators] Introducing the Ops Tags Team
Message-ID: <1432126277.2721.93.camel at bitergia.com>
Content-Type: text/plain; charset="UTF-8"

I'm not at Vancouver, but I'm interested in this wg. I've included some comments in the etherpad, mainly about opportunities for automation, and at the end a proposal on how to express tags using JSON. I would appreciate any summary from the working session.

Saludos,

        Jesus.

On Tue, 2015-05-12 at 23:04 +0800, Tom Fifield wrote:
> Hi all,
>
> By now you should have seen Thierry's "The Way Forward" blog[1], which
> describes the problems with having just one binary flag to say whether
> a project is 'good' or not (the integrated release), and proposes the
> tags system.
>
> The tags system lets us make up a series of labels for each software
> project in the OpenStack ecosystem to help people in their decision
> making. As Ops, we have a lot of knowledge about what works, and how
> it works. We're also in a good position to define what it is our
> fellow Ops actually needed to know before they choose to deploy something.
>
>
> It's my great pleasure to announce the formation of the Ops Tag Team.
>
>
> Continuing from the initial work done by the user committee and those
> of us who made it to Philadelphia[2], the Vancouver summit is the time
> to really get this effort ramped up. The team will have a working
> session to define the initial set of tags.
>
> There are a range of questions you likely have, and many an effort
> needed on scoping this activity to be the most useful it can be. I've
> attempted to kick-start some things on the etherpad for that session,
> and your edits and tag suggestions there would be appreciated:
>
> https://etherpad.openstack.org/p/YVR-ops-tags
>
>
> Please do make that etherpad as useful as possible :) The room we have
> at the summit is limited in size, and really designed for those who
> plan to make ongoing contributions to the activity to do actual work.
>
>
> Regards,
>
>
> Tom, on behalf of the User Committee
>
> [1] http://ttx.re/the-way-forward.html
> [2] https://etherpad.openstack.org/p/PHL-ops-tags
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator
> s

--
Bitergia: http://bitergia.com
/me at Twitter: https://twitter.com/jgbarah




------------------------------

Message: 3
Date: Wed, 20 May 2015 07:32:42 -0700
From: Christopher Aedo <caedo at mirantis.com>
To: "openstack-operators at lists.openstack.org"
        <openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] [App-Catalog] Planning/working session
        Wednesday in Vancouver
Message-ID:
        <CAMtawZUWoOGcScaEvov1=8dkoM+=K8jw5F9-fL45X0Q+JH+3FA at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

[Cross-posting to both dev and operators list because I believe this
is important to both groups]

For those of us who have been working on the OpenStack Community App
Catalog (http://apps.openstack.org) yesterday was really exciting.  We
had a chance to do a quick demo and walk through during the keynote,
followed by a longer talk in the afternoon (slides here:
http://www.slideshare.net/aedocw/openstack-community-app-catalog-httpappsopenstackorg)

The wiki page with more details is here:
https://wiki.openstack.org/wiki/App-Catalog

If you are in Vancouver and are interested in helping improve the
Community App Catalog please join us for this working session:

http://sched.co/3Rk4 (11:50 room 116/117)
Etherpad: https://etherpad.openstack.org/YVR-app-catalog-plans

If you can't join the session but have ideas or thoughts you would
like to see discussed please add them to the etherpad.  I've put down
a few of the ideas that have come up so far, but it's definitely not a
comprehensive list.

We got really great feedback yesterday afternoon and found a lot of
people are interested in contributing to the catalog and working
together to add improvements.  Hopefully you can join us today!

-Christopher



------------------------------

Message: 4
Date: Wed, 20 May 2015 15:21:03 +0000
From: Matt Van Winkle <mvanwink at rackspace.com>
To: "openstack-operators at lists.openstack.org"
        <openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] [Large Deployments Team]  Today's
        sessions
Message-ID: <D182108B.154A4B%mvanwink at rackspace.com>
Content-Type: text/plain; charset="iso-8859-1"

Hello folks,
Back at our last meeting, we decided to focus on three areas in or triple summit sessions today:
Capacity related specs
Cells V2 related work
General business

Not much has materialize from a capacity management perspective, so for now, I've also lumped in some time to discuss the backlog specs that John Garbutt brought up recently (http://specs.openstack.org/openstack/nova-specs/specs/backlog/)

For the Cells V2 work, Andrew Laski gave me some blueprints he'd really like feedback on, so we'll look at those and discuss anything else cells related that is important.

Instead of general business for the team, I'm taking the opportunity to get Nova, Neutron and LDT folks in the room.  This will largely be to help both Nova and Neutron devs understand how we use our networks - especially with cells - in order to further the work of getting Neutron to support our needs.  We've been working to get folks from all sides in, but we'll see if schedules allow.  In an attempt to be successful at that, I've put this session in the middle at 14:40 based on feedback from some folks we'd like there and their other commitments today.

I've thrown together as much as I can in the etherpad already

https://etherpad.openstack.org/p/YVR-ops-large-deployments


I'll be in most of the Nova design sessions this morning, so I'll add/edit as necessary based on output from those if they will influence/outweigh the things we have planned to go over.  Also, in places where nova needs operator input on the decisions being made (that isn't available at the time), I'll find a spot on our agenda to see if we can quickly close the feedback loop here at the summit.

See you this afternoon!
Matt



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150520/28534f34/attachment-0001.html>

------------------------------

Message: 5
Date: Wed, 20 May 2015 20:45:34 -0700
From: Richard Raseley <richard at raseley.com>
To: OpenStack Development Mailing List
        <OpenStack-dev at lists.openstack.org>, OpenStack Operators Mailing List
        <openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] [glance] [kolla] [magnum] [nova]
        [neutron] Vancouver Summit Operations Containers Session
Message-ID: <555D54DE.60701 at raseley.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

I apologize if this message is inappropriately broad, but I wanted to
share the results of the Vancouver Summit operations containers
session[0] we held yesterday with all of the projects which were mentioned.

This was a great discussion with approximately two-dozen individuals in
attendance. Most of the conversation was captured pretty well on the
etherpad, which can be found here:

https://etherpad.openstack.org/p/YVR-ops-containers

A big thank you to everyone who participated - it was really informative.

Regards,

Richard Raseley

SysOps Engineer @ Puppet Labs

[0] - http://sched.co/3B45



------------------------------

Message: 6
Date: Thu, 21 May 2015 05:56:04 +0100
From: Daniel Comnea <comnea.dani at gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"
        <openstack-dev at lists.openstack.org>
Cc: OpenStack Operators Mailing List
        <openstack-operators at lists.openstack.org>
Subject: Re: [Openstack-operators] [openstack-dev] [glance] [kolla]
        [magnum] [nova] [neutron] Vancouver Summit Operations Containers
        Session
Message-ID:
        <CAOBAnZN6Z2gtzatPk-0dGEE1E8kyp9-fRzdXeO52W00YA_zWHw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Great info, thanks for sharing.

Since i couldn't attend the summit, are there any AIs which needs to
happen/ take place and which i can keep an eye on?

thanks,
Dani

On Thu, May 21, 2015 at 4:45 AM, Richard Raseley <richard at raseley.com>
wrote:

> I apologize if this message is inappropriately broad, but I wanted to
> share the results of the Vancouver Summit operations containers session[0]
> we held yesterday with all of the projects which were mentioned.
>
> This was a great discussion with approximately two-dozen individuals in
> attendance. Most of the conversation was captured pretty well on the
> etherpad, which can be found here:
>
> https://etherpad.openstack.org/p/YVR-ops-containers
>
> A big thank you to everyone who participated - it was really informative.
>
> Regards,
>
> Richard Raseley
>
> SysOps Engineer @ Puppet Labs
>
> [0] - http://sched.co/3B45
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150521/e253c55f/attachment-0001.html>

------------------------------

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


End of OpenStack-operators Digest, Vol 55, Issue 23
***************************************************

________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________

www.accenture.com