Re: [Openstack-operators] [openstack-dev] Community Contributor Awards
Time is running out to nominate for an award!! https://openstackfoundation.formstack.com/forms/community_contributor_award_nomination_form On 21/09/16 02:43, Kendall Nelson wrote: Hello all, I’m pleased to announce the next round of community contributor awards! Similar to the Austin Summit, the awards will be presented by the Foundation at the feedback session of the upcoming Summit in Barcelona. Now accepting nominations! Please submit anyone you think is deserving of an award! https://openstackfoundation.formstack.com/forms/community_contributor_award_nomination_form Please submit all nominations by the end of day on October 7th. There are so many people out there who do invaluable work that should be recognized. People that hold the community together, people that make working on OpenStack fun, people that do a lot but aren’t called out for their work, people that speak their mind and aren’t afraid to challenge the norm. Like last time, we won’t have a defined set of awards so we take extra note of what you say about the nominee in your submission to pick the winners. We’re excited to hear who you want to celebrate and why you think they are awesome! All the Best, Kendall Nelson (diablo_rojo) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [kolla] Decision to deprecate Fedora
For what it's worth, RDO does not currently test deployment on top of Fedora (since Liberty at the very latest).and we also no longer ship OpenStack Service/Server components to Fedora [1]. We don't see this changing in the short term. [1]: https://www.redhat.com/archives/rdo-list/2015-September/msg00090.html David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Tue, Sep 27, 2016 at 3:02 PM, Steven Dake (stdake)wrote: > Hey folks, > > > > We are deprecating the fedora implementation in newton, and it will be > removed in Ocata. Reference: > > https://review.openstack.org/#/c/369184/ > > > > Since nobody seems to complain it is not working, it seems not worthwhile to > maintain it. At present the fedora implementation is broken. > > > > If you are currently using Kolla with Fedora (I don’t know how, it doesn’t > work) – the migration plan I’d recommend is switching to CentOS. > > > > Any objections? > > > > Regards > > -steve > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [scientific][scientific-wg] Reminder: Scientific WG meeting Wednesday 0900 UTC
Greetings all - We have a Scientific WG IRC meeting on Wednesday at 0900 UTC on channel #openstack-meeting. The agenda is available here[1] and full IRC meeting details are here[2]. This week we have discussion on federated identity management on the agenda, plus updates on Barcelona. Looking further ahead we are looking for OpenStack-centric picks from the Supercomputing 2016 conference schedule. I’d also like to continue the discussion on how we might change the way the WG works for the next cycle and gather peoples thoughts for the agenda for the Barcelona committee meeting. If anyone would like to add an item for discussion on the agenda, it is also available in an etherpad[3]. Best wishes, Stig [1] https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_September_28th_2016 [2] http://eavesdrop.openstack.org/#Scientific_Working_Group [3] https://etherpad.openstack.org/p/Scientific-WG-next-meeting-agenda ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [kolla] Decision to deprecate Fedora
Hey folks, We are deprecating the fedora implementation in newton, and it will be removed in Ocata. Reference: https://review.openstack.org/#/c/369184/ Since nobody seems to complain it is not working, it seems not worthwhile to maintain it. At present the fedora implementation is broken. If you are currently using Kolla with Fedora (I don’t know how, it doesn’t work) – the migration plan I’d recommend is switching to CentOS. Any objections? Regards -steve ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Call for Lightning Talks (BCN Operators Meetup)
Topic submissions for the general sessions at the Barcelona session are going well (see https://etherpad.openstack.org/p/BCN-ops-meetup) ... except for Lightning Talks which aren't getting many suggestions. For this reason the ops meetup team IRC meeting today decided to break them out into a separate list. Please use the following new etherpad to suggest new lightning talks for Barcelona https://etherpad.openstack.org/p/BCN-ops-lightning-talks Existing submissions were replicated across, but lost their color-coding, sorry. Lightning talks are a fun, low-stress way to broach a topic important to you and perhaps try a bit of public speaking with your peers in the community without needing to commit to a big presentation with slides and whatnot. Typically, they are 10 minutes or less. Topics are wide-ranging, including (but not limited to) : - war stories - architecture show and tell - Interesting new features of openstack related technologies Please consider doing one and sign up! Chris -- Chris Morgan___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Neutron Allow tenants to select Fixed VM IPs
Late to the party, better than ever. https://github.com/openstack/neutron/blob/master/etc/policy.json#L90 On Sun, Aug 28, 2016 at 8:29 AM, William Josefssonwrote: > yes thanks Kyle, I checked the neutron db and noticed there's a table called > ipallocations which seems to be link between port and the assigned VM IP > address. So even in the event I need to replace a crashed Neutron Networking > node, hopefully the IP addresses will be retrieved from the DB. thx will > > On Sun, Aug 28, 2016 at 12:26 AM, Kyle Greenwell wrote: >> >> If I'm not mistaken, the ip is assigned to the neutron port, and that is >> assigned to the vm. As long as the instance doesn't get blown away and >> rebuilt with a different neutron port you won't be at risk of losing the ip. >> >> Sent from my iPhone >> >> On Aug 27, 2016, at 3:23 AM, William Josefsson >> wrote: >> >> thanks Lubosz! I should explore further if floating IPs will help here. >> >> Can you also please clarify if VM IP is stored in the DB the IPs that have >> been assigned to a VM so there should be no risk of the dhcp giving it a new >> IP suddenly? That would cause a nightmare with real tenants soon coming >> onboard my deploy. I know there are some dnsmasq dhcp files in >> /var/lib/neutron/ on my Networking nodes, but what if I replace one of them >> with a fresh install, will the necessary vm details such as IP etc. be >> retrieved from the DB? thx will >> >> On Sat, Aug 27, 2016 at 12:17 AM, Kosnik, Lubosz >> wrote: >>> >>> Lubosz is my first name not Kosnik :P >>> You can create a VM from Horizon and only specify the floating IP to be >>> exactly that one. With private networks it’s not available from Horizon. >>> About getting every time the next IP it’s normal thing. After getting the >>> roof for that specified IP range it will start looking for free IPs from the >>> beginning of the range. >>> >>> Cheers, >>> Lubosz Kosnik >>> Cloud Software Engineer OSIC >>> lubosz.kos...@intel.com >>> >>> On Aug 26, 2016, at 11:06 AM, William Josefsson >>> wrote: >>> >>> Hi Kosnik. thanks. Is there any way in the GUI for the user to do that, >>> or they need to do cli 'neutron port-create ...' ? >>> Maybe I can pre-create the fixed IPs as admin, but how do a standard >>> tenant user select the Ports just created .. just as they select the >>> Networks/Subnets during 'Launch an instance'? >>> >>> I notice while provisioning that the IP number increments all the time, >>> even if previous instances with lower IPs are deleted. What will happen >>> eventually when I reach the last IP, will the lower number IPs be reused, or >>> what would the behavior be? thx will >>> >>> >>> >>> On Thu, Aug 25, 2016 at 10:58 PM, Kosnik, Lubosz >>> wrote: VM always will get the same IP from DHCP server. To prepare the VM with fixed IP you need using neutron create a port in specified network with specified IP and after that to boot new VM you’re specifying not net-id but port-id and it’s gonna work. Cheers, Lubosz Kosnik Cloud Software Engineer OSIC lubosz.kos...@intel.com On Aug 25, 2016, at 9:01 AM, William Josefsson wrote: Hi, I wonder if there's any way of allowing my users to select fixed IPs for the VMs? I do shared Provider networks, VLAN on Liberty/CentOS. I know nova boot from the CLI or API has v4-fixed-ip=ip-addr option, however is there any way in the Dashboard where the User can select static IP? I would also appreciate if anyone can explain the default dnsmasq dhcpd lease. Will a VM always get the same IP during it's life time, or it may change? thx will ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >>> >> >> ___ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News
Kudos to all! Edgar On 9/27/16, 4:14 AM, "Tom Fifield"wrote: Hi Ops Meetups Team, Thanks to everyone who contributed to the Barcelona agenda brainstorming! In our meeting today we should look at the schedule grid and plan to get our agenda out! ==Next Meeting== So, the next meeting is at: ==> Tuesday, 27 of Sep at 1400 UTC[1] in #openstack-operators [2] will be kept up to date with information about the meeting time and agenda Regards, Tom [1] https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_fixedtime.html-3Fmsg-3DOps-2BMeetups-2BTeam-26iso-3D20160927T22-26p1-3D241=DQICAg=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ=NaUk3xuXaMcURoeoVRwllnzi892M8hQmbkRe7Qg9NYc=BvMuO57HqVmS7A9qIfP_7m-baFH5304MGx7qZeJogAU= [2] https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Ops-5FMeetups-5FTeam-23Meeting-5FInformation=DQICAg=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ=NaUk3xuXaMcURoeoVRwllnzi892M8hQmbkRe7Qg9NYc=9wCRGicL6UNXZVKS3MOw7gYIOc1G4ngbrbrV6WC42CQ= ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators=DQICAg=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ=NaUk3xuXaMcURoeoVRwllnzi892M8hQmbkRe7Qg9NYc=BUBV3yDgfgO054Du7N5iVXc532CA43ScEyzyXB8Qk5U= ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News
Hi Ops Meetups Team, Thanks to everyone who contributed to the Barcelona agenda brainstorming! In our meeting today we should look at the schedule grid and plan to get our agenda out! ==Next Meeting== So, the next meeting is at: ==> Tuesday, 27 of Sep at 1400 UTC[1] in #openstack-operators [2] will be kept up to date with information about the meeting time and agenda Regards, Tom [1] http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team=20160927T22=241 [2] https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] How setup multiple memcache servers for Dashboard
Hi Alvise, you can easily add more memcache nodes like in the other OpenStack services, like: CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': ['memcache01:11211', 'memcache02:11211', 'memcache03:11211', ] }, } cheers, hauke On Dienstag, 27. September 2016 11:57:23 CEST Alvise Dorigo wrote: > Hi, > > is there a way to make the dashboard using more than one memcached > server as other components do (e.g. nova, neutron, cinder, with the > memcached_servers parameter) ? > > thank you, > > > Alvise > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- signature.asc Description: This is a digitally signed message part. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] How setup multiple memcache servers for Dashboard
Hi, is there a way to make the dashboard using more than one memcached server as other components do (e.g. nova, neutron, cinder, with the memcached_servers parameter) ? thank you, Alvise ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [openstack-hpc] What's the state of openstack-hpc now?
Hi Andrew, hi John - I've just started trying to get CUDA P2P working in our virtualized HPC environment. I figure this must be something you solved already in order to produce the aforementioned paper, but having read it a couple of times I don't think it provides enough detail about the guest config, hoping you can shed some light... The issue I'm grappling with is that despite using a qemu-kvm machine type (q35) with an emulated PCIe bus and seeing that indeed the P2P capable GPUs (NVIDIA K80s) are attached to that bus, and nvidia-smi sees them as sharing a PHB, the simpleP2P CUDA sample fails when checking their ability to communicate with each other. Is there some magic config I might be missing, did you need to make any PCI-ACS changes? Best regards, Blair On 16 March 2016 at 07:57, Blair Bethwaitewrote: > > Hi Andrew, > > On 16 March 2016 at 05:28, Andrew J Younge wrote: > > point to a recent publication of ours at VEE15 titled "Supporting High > > Performance Molecular Dynamics in Virtualized Clusters using IOMMU, > > SR-IOV, and GPUDirect." In the paper we show that using Nvidia GPUs > ... > > http://dl.acm.org/citation.cfm?id=2731194 > > Oooh interesting - GPUDirect too. That's something I've been wanting > to try out in our environment. Will take a look a your paper... > > -- > Cheers, > ~Blairo -- Cheers, ~Blairo ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators