astly, the only thing holding up the patch from
merging this week was a multitude of bugs in the gate.
Thanks,
Andrew Melton
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ing correctly, a new license simple grants access to
newer versions, current versions should still work.
Thanks for your patience,
Andrew Melton
From: Manickam, Kanagaraj [kanagaraj.manic...@hp.com]
Sent: Sunday, September 21, 2014 11:20 PM
To: OpenStack Development M
id. If you are unsure of your
situation, it may be best to hold off until I hear back from Jetbrains.
Lastly, as part of Jetbrains granting us this new license, they have asked if
anyone would be willing to write a review. If anyone would like to do that,
please let me know.
Thanks,
And
o not meet those criteria, I can provide you the key. To
request the key from me, please send me the name of the company you work for
(if applicable) and your launchpad id.
Thanks again,
Andrew Melton
____
From: Andrew Melton [andrew.mel...@rackspace.com]
Sent: Tuesday,
Hey Devs,
It's almost been a year since I sent out the first email and I've been getting
a few emails lately about alerts that the current license is about to expire.
Well, I've got a hold of our new license, good for another year. This'll give
you access to the new Pro edition of Pycharm and
ometer community is this, does this sound like
something Ceilometer would find value in and use? If so, would this be
something
we would want most deployers turning on?
Thanks,
Andrew Melton
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
{'id': 'uuid2', 'owner': 'tenant2', 'created_at':
'some_date', 'deleted_at': 'some_other_date', 'size': 2}]
That way the audit job/task could be configured to emit in batches which
a deployer could
Hey Devs,
I'm the guy who's maintained our JetBrains licenses for the past couple of
years. License philosophy aside, the IDE you choose to use is entirely up to
you. I'm currently waiting to hear back from JetBrains on the actual license.
From the sound of it, the opensource license hasn't ch
Hey Daneyon,
I'm fairly partial towards #2 as well. Though, I'm wondering if it's possible
to take it a step further. Could we run etcd in each Bay without using the
public discovery endpoint? And then, configure Swarm to simply use the internal
ectd as it's discovery mechanism? This could cut
Hi devs,
I've got the new license for the next year. As always, please reply to this
email with your launchpad-id if you would like a license.
Also, if there are other JetBrains products you use to contribute to OpenStack,
please let me know and I will request licenses.
?
--Andrew
_
:10 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] New PyCharm License
Hi Andrew,
My launchpad id is abhishek-kekane
Thank you,
Abhishek
From: Andrew Melton [andrew.mel...@rackspace.com]
Sent: Monday
: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] New PyCharm License
Hi Andrew,
My launchpad id is abhishek-kekane
Thank you,
Abhishek
From: Andrew Melton [andrew.mel...@rackspace.com]
Sent: Monday, September 21, 2015
I have it.
--Andrew
From: Jim Rollenhagen
Sent: Monday, September 21, 2015 3:19 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] New PyCharm License
On Mon, Sep 21, 2015 at 06:30:30PM +, Andrew Melton wrote:
> Ple
Hey Devs,
I now have a set of WebStorm licenses. Please reply with your launchpad-id and
I'll get you the invitation link for WebStorm.
--Andrew
From: Andrew Melton
Sent: Tuesday, September 22, 2015 1:43 PM
To: OpenStack Development Mailing List
Hi Devs,
I will be starting a new job in a couple weeks, and as such will be leaving my
current job and the OpenStack community by the end of this week. That means we
will need a new representative to manage the Open Source licenses JetBrains has
given us, and to manage that relationship. So,
Hey Devs,
Thanks again to those who expressed interest in taking this over! I've found a
Core who was willing to take this over, Swapnil Kulkarni. For JetBrains
licenses going forward please contact him at 'm...@coolsvap.net'.
Thanks!
Andrew
__
I think Sylvain is getting at an important point. Magnum is trying to be as
agnostic as possible when it comes to selecting a backend. Because of that, I
think the biggest benefit to Magnum would be a generic scheduling interface
that each pod type would implement. A pod type with a backend prov
x27;t post it directly to the mailing list. So,
if you would like
to use WebStorm, please send me a reply including your full name and
launchpad-id.?
Thanks!
Andrew Melton
__
OpenStack Development Mailing List (not for
???Hi Jay,
Magnum Bays do not currently use the docker-swarm template. I'm working on a
patch to add support for the docker-swarm template. That is going to require a
new TemplateDefinition, and potentially some new config options and/or
Bay/BayModel parameters. After that, the Docker containe
Hi Devs,
I'd like to get some discussion going for possible improvements to the
discovery mechanism used in Magnum's Swarm bay.
The method of the existing review[1] is to use the public swarm discovery
endpoint, and let the user pass a token in on the bay-create call. This is
definitely not
20 matches
Mail list logo
