You can't upload directly. You have to follow the same gerrit review
process as submitting regular code.
Run 'git review' from the root of the neutron-specs folder.
--
Kevin Benton
On Fri, Apr 18, 2014 at 10:47 PM, Nader Lahouti wrote:
> Do I need any permission to upload a design specification
Hi Anita-
I did not receive any mail for vote. Is there any process to do from my end to
vote.
--
Trinath Somanchi - B39208
[email protected] | extn: 4048
-Original Message-
From: Anita Kuno [mailto:[email protected]]
Sent: Friday, April 18, 2014 8:53 PM
To: OpenStack D
On 04/19/2014 05:42 AM, [email protected] wrote:
> Hi Anita-
>
> I did not receive any mail for vote. Is there any process to do from my end
> to vote.
Yes.
Please read this section of my original email.
What to do if you don't see the email and have a commit in at least one
of the
Hi Anita-
I have check the spam and junk emails .. None have the ballot email.
Here are the gerrit details
Usernametrinaths
Full Name Trinath Somanchi
Email Address [email protected]
Registered Sep 2, 2013 12:35 PM
Account ID 8645
Can you kindly please che
On 04/19/2014 10:03 AM, [email protected] wrote:
> Hi Anita-
>
> I have check the spam and junk emails .. None have the ballot email.
>
> Here are the gerrit details
>
> Username trinaths
> Full Name Trinath Somanchi
> Email Address [email protected]
> Register
Hi Kyle,
I built template and it looks awesome. We are considering to use same
approach for Fuel.
My assumption is that spec will be on review for a negotiation time, which
is going to be quite a while. In my opinion, it is not always very
convenient to read spec in gerrit.
Did you guys have any
Hi, all
When creating heat stacks, we need to specify the template path or URL, that's
always inconvenient. I suggest that the heat templates should be managed in the
background, just like the flavors in nova.
We can supply APIs for getting, putting, adding and deleting current templates
in th
Gouzongmei wrote on 04/19/2014 10:37:02 PM:
> We can supply APIs for getting, putting, adding and deleting current
> templates in the system, then when creating heat stacks, we just
> need to specify the name of the template.
Look for past discussion of Heat Template Repository (Heater). Here
