On 8/30/2013 12:49 PM, Murali Balcha wrote:
Hi Caitlin,
Did you get a chance to look at the wiki? It describes the raksha functionality
in detail.
> It includes more than volume backup. It includes vm images, all
> volumes and network configurations associated with vms and it
> supports increme
Thank you very much! It really helps me.
Regards,
Toshiyuki
On Wed, Aug 28, 2013 at 12:33 PM, Gabriel Hurley
wrote:
> If you look at the code in the post()[1] method of the base workflow view
> you'll note that a response to a successful workflow POST is always a
> redirect[2] (caveat for when
I have the same problem too. Any hints are appreciated!
https://review.openstack.org/#/c/38803/
Lingxian Kong
Huawei Technologies Co.,LTD.
IT Product Line CloudOS PDU
China, Xi'an
Mobile: +86-18602962792
Email: konglingx...@huawei.com
Hi,
If a plugin has its own extension, what is the correct way to set
api_extensions_path.
I can see at multiple places that the practice is this:
api_extensions_path=neutron//extensions/
But if you do that problem mentioned in the following bug starts appearing.
https://bugs.launchpad.net/neutr
Hi folks
I found the fix.
warlock is out-to-date in my env.
sudo pip install --upgrade warlock
fixes issue.
2013/8/30 Nachi Ueno :
> Hi folks
>
> Is anybody facing this issue?
>
> I got when I boot nova-api
>
> VersionConflict: (jsonschema 1.3.0
> (/usr/local/lib/python2.7/dist-packages),
> Req
Hi folks
Is anybody facing this issue?
I got when I boot nova-api
VersionConflict: (jsonschema 1.3.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('jsonschema>=0.7,<1'))
so, I did,
sudo pip install --upgrade jsonschema==0.8.0
then I got,
VersionConflict: (jsonschema 0.8.0
(/usr
The Marconi project team normally holds a weekly meeting in
#openstack-meeting-alt on Mondays at 1600 UTC.
Next week we won't be having a meeting due to a lot of people
being on holiday.
Cheers,
Kurt G. / kgriffs
___
OpenStack-dev mailing list
OpenS
Heat devs,
There's been some good discussion on the Etherpad:
https://etherpad.openstack.org/vJKcZcQOU9
I've added a "Votes" section under alternate options 1-5. Please read
over the discussion and add your vote.
Thanks,
Jason
On Thu, Aug 29 2013, Jason Dunsmore wrote:
> Heat devs,
>
> Liang
On 8/29/2013 5:36 PM, Murali Balcha wrote:
Hi Kat,
Consider the following use cases that Raksha will addresses. I will discuss
from simple to complex use case and then address your specific questions with
inline comments.
1.VM1 that is created on the local file system with a cinder volume
Hi Caitlin,
Did you get a chance to look at the wiki? It describes the raksha functionality
in detail. It includes more than volume backup. It includes vm images, all
volumes and network configurations associated with vms and it supports
incremental backups too. Volume backup is essential for im
I've done some additional debugging/testing, and the issue is definitely in the
savanna provisioning code.
I have verified that the correct inputs are provided to the validate_scaling
method invocation, and that those references remain unaltered. The scaling
request involves adding one node of
Congratulations to Tomas Sedovic, new Tuskar PTL.
Please find the results here:
http://www.cs.cornell.edu/w8/~andru/cgi-perl/civs/results.pl?id=E_0f2009f8cf25ef02
Please see the wiki page about this election here.
https://wiki.openstack.org/wiki/Tuskar_PTL_Elections_Summer_2013#Results
Thank
Hi folks,
I'm glad to announce two new members of savanna core team - Matthew Farrellee
from Red Hat and John Speidel from Hortonworks. They both have done a
significant contribution to Savanna especially in the area of architecture and
design.
So, currently Savanna core team consists of four
I am currently working this bug and I have a question about the scope of
the changes. The original description of the bug deals with constants
defined as TYPE_FLAT in multiple locations with the same value. It is
desired to have said constant put into common/constants.py and shared for
DRY-sake. I
Excerpts from Chan, Winson C's message of 2013-08-30 07:23:18 -0700:
> The ideal I think is to just use some random short id for the name of the
> instances and then store a creation timestamp somewhere with the resource and
> use the timestamp to determine the age of the instances for removal.
On Fri, Aug 30, 2013 at 8:02 AM, Murali Balcha wrote:
> Hi John,
> Thanks for your comments. I am planning to attend summit we can have a
> wider discussion there.
>
> Thanks,
> Murali Balcha
>
>
> On Aug 30, 2013, at 12:05 AM, "John Griffith"
> wrote:
>
>
>
>
> On Thu, Aug 29, 2013 at 6:36 PM,
Hi,
I'm seeing an issue with the migration script:
2032abe8edac_lbaas_add_status_des.py
Output from devstack is here:
http://paste.openstack.org/show/45476/
I believe the issue is that the original migration script that creates
the lbaas tables (54c2c487e913_lbaas.py) has an empty migration_fo
Context: https://review.openstack.org/#/c/43571/
On 30/08/13 16:23, Chan, Winson C wrote:
Regarding the last set of comments on the UpdatePolicy, I want to bring your
attention to a few items. I already submitted a new patch set and didn't want
to reply on the old patch set so that's why I em
Now that we have achieved the goal of parallel tempest in the gate using
testr we have to be careful that we don't introduce tests that are
flaky. This may be obvious to many of you but we should include some
information in the tempest README. Here is a start. Improvements are
welcome and I wi
I found this launchpad discussion, in which Aaron mentioned about network
awareness integration with nova cells.
https://answers.launchpad.net/neutron/+question/228815
Could anyone share some pointers in that direction? Thanks!
Best Regards,
--
Qiu Yu
On Fri, Aug 30, 2013 at 6:40 AM, Ravi Chun
Nevermind, my neutron repo was stale, didn't pick up the fix. Sorry for
the noise
--
Sean M. Collins
pgpntP9YLx4nR.pgp
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailma
Regarding the last set of comments on the UpdatePolicy, I want to bring your
attention to a few items. I already submitted a new patch set and didn't want
to reply on the old patch set so that's why I emailed.
As you are aware, IG/ASG currently create instances by appending group name and
#.
On 08/30/2013 09:22 AM, Julien Danjou wrote:
On Fri, Aug 30 2013, Russell Bryant wrote:
This is something we could get better at across all of OpenStack.
I've been thinking about proposing requiring docs *somewhere* for
everything that affects docs. For small stuff, it could be explaining
it
Hi John,
Thanks for your comments. I am planning to attend summit we can have a wider
discussion there.
Thanks,
Murali Balcha
On Aug 30, 2013, at 12:05 AM, "John Griffith"
mailto:john.griff...@solidfire.com>> wrote:
On Thu, Aug 29, 2013 at 6:36 PM, Murali Balcha
mailto:murali.bal...@trili
On Fri, Aug 30 2013, Anne Gentle wrote:
> I'd like to get docs closer to code all the time, but Sphinx hasn't met a
> few crucial requirements: translation, content reuse, PDF, and comment
> integration. I'd rather have repos and docs by audience than by project. To
> repeat, people come to docs.o
I applaud Julien's note and we're happy to work with the teams on finding
where docs should go. Julien's feeling very behind, and I'm sure other
projects are feeling the same.
We all have to set priorities. Here's where I'd start.
Log doc bugs in openstack-manuals for:
installation
configuration
On Fri, Aug 30, 2013 at 8:31 AM, Julien Danjou wrote:
> On Fri, Aug 30 2013, Davanum Srinivas wrote:
>
> > How about mandating that when one adds a DocImpact in a review it should
> > have a url to an etherpad/wiki with sufficient information for the doc
> > team? yes, +1 to let docs team figure
On Fri, Aug 30 2013, Davanum Srinivas wrote:
> How about mandating that when one adds a DocImpact in a review it should
> have a url to an etherpad/wiki with sufficient information for the doc
> team? yes, +1 to let docs team figure out where to fit it into existing
> guides.
That's a possibility
How about mandating that when one adds a DocImpact in a review it should
have a url to an etherpad/wiki with sufficient information for the doc
team? yes, +1 to let docs team figure out where to fit it into existing
guides.
-- dims
On Fri, Aug 30, 2013 at 9:01 AM, Russell Bryant wrote:
> -
On Fri, Aug 30 2013, Russell Bryant wrote:
> This is something we could get better at across all of OpenStack.
>
> I've been thinking about proposing requiring docs *somewhere* for
> everything that affects docs. For small stuff, it could be explaining
> it especially well in the commit message.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/30/2013 08:39 AM, Julien Danjou wrote:
> Hi team,
>
> We need to get better at documentation. We are terrible at it. We
> let code go through the gates knowing that our documentation isn't
> up to date. We have features implemented 6 months ago
Hi team,
We need to get better at documentation. We are terrible at it. We let
code go through the gates knowing that our documentation isn't up to
date. We have features implemented 6 months ago still not documented.
Nobody's going to do it for us.
Therefore I strongly suggest that as soon as yo
+1 for balsamiq
- Original Message -
From: "Sergey Lukjanov"
To: "OpenStack Development Mailing List"
Sent: Friday, August 30, 2013 12:54:28 AM
Subject: Re: [openstack-dev] Horizon - Mockup tool
I'm using balsamiq to make mockups.
Sincerely yours,
Sergey Lukjanov
Savanna Technical
On 29/08/13 22:31, Endre Karlson wrote:
> Does anyone know what too is used to do mockups ?
I'd suggest pencil to you.
http://pencil.evolus.vn/
Matthias
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/
Hi, everyone!
We have created a proposal for Climate REST API
https://docs.google.com/document/d/1U36k5wk0sOUyLl-4Cz8tmk8RQFQGWKO9dVhb87ZxPC8/
And we like to discuss it with everyone.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http:/
35 matches
Mail list logo
