Dan,
sure, I did not mean that we should collect this information without
understanding the workloads happening on the cloud, but still this is very
interesting information to gather.
Cheers,
Dina
On Thu, Nov 19, 2015 at 1:52 AM, Dan Smith wrote:
> > As providing OpenStack community with under
I've been looking into changing the search domain provided by the dhcp service
that is propagated to /etc/resolv.conf via dhcp in openstack.
The documentation points to changing dhcp_domain in dhcp_agent.ini but would
that not result in all projects and all dhcp agents in openstack sending out
I believe this is coming in Liberty, based on this talk:
https://www.openstack.org/summit/tokyo-2015/videos/presentation/get-your-instance-by-name-integration-of-nova-neutron-and-designate
On Thu, Nov 19, 2015 at 7:10 AM, Davíð Örn Jóhannsson
wrote:
> I've been looking into changing the search
On 11/18/2015 04:19 AM, Jesse Pretorius wrote:
> The current community has done some research into appropriate patterns to use
> and has a general idea of how to do it - but in order to actually execute
> there need to be enough people who commit to actually maintaining the work
> once it's done
I don't believe we should have a class system in the OS's that we choose
to support. If we're going to bring in a new OS I think we should first
bring it in using non-voting jobs however once all of the bits have been
finalized the supported OS should be able to pass the same sets of tests
as e
We recently patched Nova for support of server groups under cells v1. It’s
pretty rudimentary, but it works.
For anyone that’s interested, the patch is here:
https://gist.github.com/misterdorm/5e9513bb1211b49e551c and I did a short
write-up with some details at
http://www.dorm.org/blog/nova-
Several folks will be unavailable (including me) during the regular meeting
time today, so unless someone else can volunteer to run the meeting, I think we
should cancel.
Here are some status updates on things since the summit:
* Neutron segmented/routed networks
* The spec [1] is still being
FYI I also submitted https://review.openstack.org/#/c/247725/ to add our
meeting to the consolidated meeting schedule at http://eavesdrop.openstack.org/
Mike
On 11/19/15, 11:14 AM, "Mike Dorman" wrote:
>Several folks will be unavailable (including me) during the regular meeting
>time toda
Thanks, Mike. I am cool if we cancel. I will update the wiki with the info
below and we can pick back up next month
Sent from my iPhone
> On Nov 19, 2015, at 12:17 PM, Mike Dorman wrote:
>
> Several folks will be unavailable (including me) during the regular meeting
> time today, so unless
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/3/15 11:48 AM, Mike Perez wrote:
> On 18:51 Oct 28, Mike Perez wrote:
>> On 12:35 Oct 28, JJ Asghar wrote:
>>> On 10/28/15 10:35 AM, Mike Perez wrote:
On 14:09 Oct 16, hittang wrote:
> Hello,everynoe. Can anybody help me for installing
Just a reminder the ops guide meeting will start in 5 minutes in
#openstack-meeting-3.
Thanks!
Darren___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
So I can start Nova on Ubuntu/Icehouse via *$ sudo python
/usr/bin/nova-compute* and it runs fine and stays online but it does not
run/stay online if I use *$ sudo service nova-compute start/restart*.
I guessed it might have been related to rootwrap but I ran out of time to
troubleshoot so I rever
Sorry this doesn't thread properly, but cut and pasted out of the digest...
> As providing OpenStack community with understandable recommendations
> and instructions on performant OpenStack cloud deployments is part of
> Performance Team mission, I'm kindly asking you to share your
> experien
Thanks both Armando and Matt!
I am cross posting this to the operators' list (as the main post -- operators,
simple reply and no spam to dev).
The logging tag should be a tag in all projects. I'm glad it's already there
in Neutron. And, this sort of feedback is exactly what we need operators
Hi Adam,
I've seen this happen due to permission issues. Regardless of running with
sudo, upstart is dropping to the "nova" user.
I usually debug this by setting a shell on the nova user, sudoing/su'ing to
nova, then running nova-compute from there. It should die with an error
message of the caus
On 19/11/15 08:38, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote:
Hello operator friends,
We're laying out our 2016 roadmaps now, and one of the projects the
Bloomberg cloud team would like to undertake is migrating from our
legacy nova-network setup to Neutron. Our current networking is pretty
simple, w
Ops,
In case you were interested in going through specs for your favourite
project (or feature), many of them are happening around this time.
eg nova is at
https://review.openstack.org/#/q/status:open+AND+project:openstack/nova-specs,n,z
and you can find other project repos by changing nova
Thanks, JJ!
It looks like David Wahlstrom submitted a script and there's a question
about license.
https://review.openstack.org/#/c/247823/
Though contributions to contrib do not have to follow a certain coding
style, can be very lax on error handling, etc, should they at least mention
a license
Is there a reason why we can't license the entire repo with Apache2 and if
you want to contribute you agree to that? Otherwise it might become a bit
of a nightmare. Or maybe at least do "Apache2 unless otherwise stated"?
On Thu, Nov 19, 2015 at 9:17 PM, Joe Topjian wrote:
> Thanks, JJ!
>
> It l
+1 for the "unless otherwise stated" bit. I seem to recall some
non-standard requirements from the likes of HP. Apache should be a good
default though.
-Erik
On Nov 19, 2015 11:31 PM, "Matt Fischer" wrote:
> Is there a reason why we can't license the entire repo with Apache2 and if
> you want to
On 20/11/15 12:29, Matt Fischer wrote:
Is there a reason why we can't license the entire repo with Apache2 and
if you want to contribute you agree to that? Otherwise it might become a
bit of a nightmare. Or maybe at least do "Apache2 unless otherwise stated"?
According to http://www.apache.org
Unless there's a reason why we *can't* do something like that (I have no
idea why, but I never assume anything when it comes to things like
licensing :) then I'm in favor of updating the README to state "Your code
will be licensed under Apache 2 unless you mention otherwise."
On Thu, Nov 19, 2015
22 matches
Mail list logo
