Re: [openstack-dev] Manual to build an application on open stack

2013-11-02 Thread Krishanu Dhar
Thanks Denis. So,this is what I am planning. An application; I was thinking of writing it up in java 'coz I ain't that good in python. It could be accessed either via a web browser or an app could be downloaded to a desktop. Brief set of functionalities... 1. A db backend to store information retr

Re: [openstack-dev] [Heat] Network topologies

2013-11-02 Thread Edgar Magana
Zen, Kevin, Aaron, Salvatore et al, Thank you so much for taking some time and reviewing this proposal. I couldn't get any time slot neither in Neutron nor Heat track to have a deep discussion about this proposal. My conclusions are the following: - This API should be allocated in Heat project, a

[openstack-dev] Congress: an open policy framework

2013-11-02 Thread Tim Hinrichs
Hi OpenStackers, We've been working on an open policy framework for OpenStack that we're calling Congress. We've been talking with OpenStack users and several of our partners to understand the kinds of rules and regulations they envision enforcing with a policy-based management framework. Acr

Re: [openstack-dev] [Solum] Logging Blueprint Approval

2013-11-02 Thread Russell Bryant
On 11/02/2013 01:42 AM, Adrian Otto wrote: > Team, > > We have a blueprint for logging architecture within Solum, which is an > important feature to aid in debugging at runtime: > > https://blueprints.launchpad.net/solum/+spec/logging The Implementation field of the blueprint says "Needs Code R

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-11-02 Thread Russell Bryant
On 10/31/2013 04:45 AM, Alan Kavanagh wrote: > Sorry Russell but I have to ask, what is the different you see between > "traditional datacenter virtualization" and "cloud". IMHO the two co-exist > and Cloud (the buzz word that it is) is the umbrella for all encompassing > data center. That said

Re: [openstack-dev] [Heat] Do we need to clean up resource_id after deletion?

2013-11-02 Thread Randall Burt
My thoughts exactly. I meant to dig into the soft-delete code to see if those changes handled resource_id differently but I got to traveling and forgot. IMO, if it universally needs doing, then it should be done in resource.Resource and be cognizant of deletion policy. __

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-11-02 Thread Russell Bryant
On 10/30/2013 11:51 PM, Mike Spreitzer wrote: > Swapnil Kulkarni wrote on 10/30/2013 > 02:36:37 AM: > >> I had a discussion with russellb regarding this for yesterday, I >> would like to discuss this with the team regarding the blueprint >> mentioned in subject. >> >> > https://blueprints.launchp

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-11-02 Thread Russell Bryant
On 10/30/2013 11:35 PM, Daniel P. Berrange wrote: > On Wed, Oct 30, 2013 at 04:20:34AM -0400, Russell Bryant wrote: >> On 10/30/2013 03:13 AM, Alex Glikson wrote: >>> Maybe a more appropriate approach could be to have a tool/script that >>> does it, as a one time thing. >>> For example, it could ma

Re: [openstack-dev] [Solum] Choice of API infrastructure

2013-11-02 Thread Russell Bryant
On 11/02/2013 11:54 AM, Adrian Otto wrote: > Noorul, > > I agree that key decisions should be tracked in blueprints. This is the > one for this decision which was made in our 2013-10-18 public meeting. > Jay's submission is consistent with the direction indicated by the team. > > https://blueprin

Re: [openstack-dev] [neutron] [qa] gate-tempest-devstack-vm-neutron-pg-isolated failing 45% of the time

2013-11-02 Thread Sean Dague
Thanks for diving into this one guys! Very much appreciated. -Sean On 11/02/2013 02:22 AM, Armando Migliaccio wrote: > I think/hope I nailed it down. Once more patch coming right up! > > > On Fri, Nov 1, 2013 at 11:15 AM, Salvatore Orlando wrote: > >> Hi Sean, >> >> I looked further ye

Re: [openstack-dev] [Solum] Create a source repo for the API specification?

2013-11-02 Thread Rajesh Ramchandani
+1 Couldn't agree more. Christopher Armstrong wrote: On Sat, Nov 2, 2013 at 4:39 PM, Jay Pipes mailto:jaypi...@gmail.com>> wrote: Hi all, One of the most important aspects in the early stages of Solum development will be the consensus building and stabilization of the Solum API specificatio

Re: [openstack-dev] [Solum] Call for participation: Breakout meeting for API deep-dive

2013-11-02 Thread Adrian Otto
Team, The dates have been chosen based on your feedback: https://wiki.openstack.org/wiki/Solum/BreakoutMeetings#Solum_API_Deep_Dive Please mark your calendars for 2100 UTC on 2013-11-13 and 2013-11-15. We will meet in #solum. Thanks, Adrian On Oct 31, 2013, at 11:35 AM, Adrian Otto wrote:

Re: [openstack-dev] [Solum] Create a source repo for the API specification?

2013-11-02 Thread Clayton Coleman
+1 - with the level of interest among existing vendors I think this will help others who want to be API compatible with Solum (above and beyond normal benefits) > On Nov 2, 2013, at 5:48 PM, Jay Pipes wrote: > > Hi all, > > One of the most important aspects in the early stages of Solum develo

Re: [openstack-dev] [Solum] Create a source repo for the API specification?

2013-11-02 Thread Christopher Armstrong
On Sat, Nov 2, 2013 at 4:39 PM, Jay Pipes wrote: > Hi all, > > One of the most important aspects in the early stages of Solum development > will be the consensus building and stabilization of the Solum API > specification. A solid API spec aid in the speeding up the pace of > innovation in the So

Re: [openstack-dev] [Solum] Create a source repo for the API specification?

2013-11-02 Thread Adrian Otto
Jay, On Nov 2, 2013, at 2:39 PM, Jay Pipes wrote: > Hi all, > > One of the most important aspects in the early stages of Solum development > will be the consensus building and stabilization of the Solum API > specification. A solid API spec aid in the speeding up the pace of innovation > in

[openstack-dev] [Solum] Create a source repo for the API specification?

2013-11-02 Thread Jay Pipes
Hi all, One of the most important aspects in the early stages of Solum development will be the consensus building and stabilization of the Solum API specification. A solid API spec aid in the speeding up the pace of innovation in the Solum contributor community. One of the aspects of the Key

Re: [openstack-dev] [Heat] Network topologies

2013-11-02 Thread Salvatore Orlando
Hi. I looked at the detailed API specification submitted by Edgar. I think that the document Edgar shared does a fine job in discussion how an API for managing logical topologies should work. On the other hand, there are two aspects which still need some clarification, and which perhaps are at the

Re: [openstack-dev] [Solum] Tracking technology choices using blue prints

2013-11-02 Thread Jay Pipes
On 11/01/2013 09:55 PM, Noorul Islam K M wrote: I was looking at the review [1]. And at that point I vaguely remembered a discussion on IRC about framework choice for WSGI. But those discussions are not captured in document and brought to conclusion. So, I think it will be great, if we create bl

Re: [openstack-dev] [qa][keystone] Help with XML Tempest API tests

2013-11-02 Thread Adam Young
On 11/01/2013 04:58 AM, Steven Hardy wrote: On Thu, Oct 31, 2013 at 09:40:46PM -0400, Adam Young wrote: I think it is safe to say that the trusts API is broken in XML. I added the following test: diff --git a/keystone/tests/test_v3_auth.py b/keystone/tests/test_v3_auth.py index c0e191b..6a0c1

Re: [openstack-dev] [neutron][ceilometer] Network Notification plugin broken. Ceilometer bug #1243292

2013-11-02 Thread Eoghan Glynn
Sphoorti, Just copying the list with some pointers on this issue that I gave you on IRC. Running 'neutron router-update' show that the tenant ID is absent from the 'router.update.start' but present in the 'router.update.end' notification. Note that the logic to send the update.start notificatio

Re: [openstack-dev] [Solum] Some initial code copying for db/migration

2013-11-02 Thread Russell Bryant
On 11/01/2013 12:46 PM, Clayton Coleman wrote: >>> I was also going to throw in migrate as a dependency and put in the glue >>> code for that based on common use from ironic/trove/heat. That'll pull in >>> a few openstack common and config settings. Finally, was going to add a >>> solum-dbsync co

Re: [openstack-dev] [Solum] Some initial code copying for db/migration

2013-11-02 Thread Russell Bryant
On 11/01/2013 05:50 PM, Michael Still wrote: > On Sat, Nov 2, 2013 at 3:30 AM, Russell Bryant wrote: > >> I also would not use migrate. sqlalchemy-migrate is a dead upstream and >> we (OpenStack) have had to inherit it. For new projects, you should use >> alembic. That's actively developed and

[openstack-dev] [heat][keystone] APIs, roles, request scope and admin-ness

2013-11-02 Thread Steven Hardy
Hi all, Looking to start a wider discussion, prompted by: https://review.openstack.org/#/c/54651/ https://blueprints.launchpad.net/heat/+spec/management-api https://etherpad.openstack.org/p/heat-management-api Summary - it has been proposed to add a management API to Heat, similar in concept to t

Re: [openstack-dev] Migrating to newer full projects from what used to be part of nova

2013-11-02 Thread Thomas Goirand
On 11/01/2013 11:02 AM, Dean Troyer wrote: > To clarify a bit, while deprecated, nova-network has not lost any > functionality in Havana yet. It also hasn't gained much (if any), but > it still works. The majority of the testing is performed using > nova-network and not neutron (yet). It is also

Re: [openstack-dev] Migrating to newer full projects from what used to be part of nova

2013-11-02 Thread Scott Devoid
> > Migrations from Essex to Grizzly/Havana ... I would find it entirely suitable to upgrade from Essex to Folsom, then > migrate from nova-volume to cinder and from nova-network to quantum, then > only to upgrade to Grizzly. We're in the same spot, upgrading an Essex deployment to Havana. We d

Re: [openstack-dev] Manual to build an application on open stack

2013-11-02 Thread Denis Makogon
Ok, i got it. I'd suggest you to describe whole copcent of your application (if it is not commercial secret) and let community lead you to right direction. There simple rules of developing with OpenStack: 1. Python based. 2. Clinet/Server interaction 3. ReST 4. Test coverage. Inner test or Tempest.

[openstack-dev] Re : Re: Manual to build an application on open stack

2013-11-02 Thread Romain Hardouin
> I am trying to build an app that resides on the cloud and would want to > perform some basic storage management operations. So, you want to > build an app atop Swift ?-Romain___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://li

Re: [openstack-dev] Manual to build an application on open stack

2013-11-02 Thread Krishanu Dhar
Sorry for being vague in my previous email. Thanks for the link, I'll go through it. I am trying to build an app that resides on the cloud and would want to perform some basic storage management operations. On Sat, Nov 2, 2013 at 3:07 PM, Denis Makogon wrote: > It depends on what kind of appli

Re: [openstack-dev] Manual to build an application on open stack

2013-11-02 Thread Denis Makogon
It depends on what kind of application your are building. There serveral way of developing something above openstack services. I hope this wikinpage would help you a bit https://wiki.openstack.org/wiki/Documentation 2013/11/2 Krishanu Dhar > Hi, > > I wanted to build an application on openstack

[openstack-dev] Manual to build an application on open stack

2013-11-02 Thread Krishanu Dhar
Hi, I wanted to build an application on openstack and wanted help on how do i go about doing it? Since i am absolutely new to the stack I was wondering if their is a developer's manual or something of that sort. All I have done so far is started the installation of devstack. I am typing this emai