da Agency

Docker SF Meetup #47; Docker 1.12, Docker for Mac and Tugbot

On Wednesday members of the #Docker SF #Meetup community joined us at Docker HQ for our 47th Docker meetup in San Francisco! It was a great evening with talks and demos from Docker’s own Ben Bonnefoy, Nishant Totla, as well as Neil Gehani from HPE.

Ben Bonnefoy is currently working on Docker for #Mac and Docker for #Windows, which were released in beta in March. At the meetup, he gave an insight into the new features as well as the open source components used under the hood namely:

HyperKit ™: A lightweight virtualization toolkit on OSX
DataKit ™: A modern pipeline framework for distributed components
VPNKit ™: A library toolkit for embedding virtual networking

 
.@FrenchBen talking at the SF @docker meetup on Insight into Docker for Mac and Docker for Windows! pic.twitter.com/oQ0pkD6P8k— Docker (@docker) August 4, 2016
In case you missed it, Docker 1.12 was made generally available on July 28! Nishant Totla, who works on the core open source team and is currently working on Docker Swarm, spoke after Ben and gave attendees all the latest updates on Docker 1.12. Take a look at his slides on the new features below.

 
.@nishanttotla talks updates on Docker 1.12 at SF @Docker meetup! pic.twitter.com/f9Lx7QeXDI— Docker (@docker) August 4, 2016
The third talk and final talk of the evening was by a guest speaker, Neil Gehani, from HPE. Neil’s talk was on ‘Tugbot’, an in-cluster #container testing framework. To find out more, view Neil’s slides below.

 
.@gehaniNeil of @HPE at @docker meetup introduces "Tugbot" in-cluster container testing! pic.twitter.com/REstXvopgR— Docker (@docker) August 4, 2016
For those of you who would like to watch the talks and see the demos in full, we also recorded the meetup so feel free to watch and share!

 
Thank you speakers @FrenchBen @nishanttotla @GehaniNeil @HPE & the attendees who joined our @docker meetup 2night! pic.twitter.com/BjW0WVXItw— Docker (@docker) August 4, 2016

New blog post w/ video & slides from #dockerSF meetup w/ @frenchben @Nishanttotla @GehaniNeilClick To Tweet

Quelle: https://blog.docker.com/feed/

da Agency

Amazon ElastiCache now supports the M4 node family

Amazon ElastiCache now supports M4 node types. M4 nodes provide a balance of compute, memory, and network resources. They come in 5 sizes, ranging from 6.42 GB to 154.64 GB of memory, and have superior performance and lower prices than M3 node types. You can purchase M4 node types as On Demand or as Reserved Cache Nodes.
Quelle: aws.amazon.com

da Agency

AWS Database Migration Service Now Available in Asia Pacific (Seoul), Asia Pacific (Mumbai) and South America (São Paulo)

AWS Database Migration Service is now available to customers in the AWS Asia Pacific Seoul and Mumbai regions, as well as the South America region in São Paulo. AWS Database Migration Service helps you migrate databases to AWS easily and securely. The source database remains fully operational during the migration, minimizing downtime to applications that rely on the database.
Quelle: aws.amazon.com

da Agency

Specifying the VPC for your Amazon RDS DB Instance

You can now easily change the Amazon Virtual Private Cloud (Amazon VPC) used by your Amazon RDS DB instance. You can specify a new VPC for an existing DB instance deployed in Single-AZ configuration by using the Amazon RDS Management Console, the Amazon RDS API, or the AWS Command Line Tools. In addition, if you are running your DB instance on the EC2-Classic environment, you can switch to the EC2-VPC environment by modifying your existing DB instance. If your AWS account was created before 2013-12-04, you are potentially running RDS on the EC2-Classic environment.
Quelle: aws.amazon.com

da Agency

GameLift Adds Game Session Search

Amazon GameLift is a fully managed service that makes it simple and cost-effective to deploy, operate, and scale session-based multi-player game servers in the cloud. GameLift has added two new features and made several improvements to the service. Game developers can now use the new game session search & sort feature to populate session browsers with active game sessions that better match player preferences. Developers building game servers can now implement custom health checks for game server processes and report health status, which GameLift uses to track and maintain overall health for a fleet. In addition, with the release of the new Server SDK, GameLift now fully supports the ability to run multiple server processes concurrently on each instance in a fleet, giving you greater control over how efficiently you use GameLift resources and potentially reducing overall costs for hosting your game.
Quelle: aws.amazon.com

da Agency

OpenStack Developer Mailing List Digest June 18-24

Status of the #OpenStack Port to Python 3

The only projects not ported to Python 3 yet:

Nova (76%)
Trove (42%)
Swift (0%)

Number of projects already ported:

19 Oslo Libraries
4 development tools
22 OpenStack Clients
6 OpenStack Libraries (os-brick, taskflow, etc)
12 OpenStack services approved by the TC
17 OpenStack services (not approved by the TC)

Raw total: 80 projects
Technical Committee member Doug Hellmann would like the community to set a goal for Ocata to have Python 3 functional tests running for all projects.
Dropping support for Python 2 would be nice, but is a big step and shouldn&8217;t distract from the goals of getting the remaining things to support Python 3.

Keep in mind OpenStack on PyPy which is using Python 2.7.

Full thread

Proposal: Architecture Working Group

OpenStack is a big system that we have debated what it actually is [1].
We want to be able to point to something and proud tell people “this is what we designed and implemented.”

For individual projects this is possible. Neutron can talk about their agents and drivers. Nova can talk about conductors that handle communication with compute nodes.
When we talk about how they interact with each other, it&8217;s a coincidental mash of de-facto standards and specs. They don&8217;t help someone make decisions when refactoring or adding on to the system.

Oslo and cross-project initiatives have brought some peace and order to implementation, but not the design process.

New ideas start largely in the project where they are needed most, and often conflict with similar decisions and ideas in other projects.
When things do come to a head these things get done in a piecemeal fashion, where it&8217;s half done here, 1/3 over there, ¼ there, ¾ over there.
Maybe nova-compute should be isolated from Nova with an API Nova, Cinder and Neutron can talk to.
Maybe we should make the scheduler cross-project aware and capable of scheduling more than just Nova.
Maybe experimental groups should look at how some of this functionality could perhaps be delegated to non-OpenStack projects.

Clint Byrum would like to propose the creation of an Architecture Working Group.

A place for architects to share their designs and gain support across projects to move forward and ratify architectural decisions.
The group being largely seniors at companies involved and if done correctly can help prioritize this work by advocating for people/fellow engineers to actually make it &8216;real&8217;.

How to get inovlved:

Bi-weekly IRC meeting at a time convenient for the most interested individuals.
openstack-architecture channel
Collaborate on the openstack-specs repo.
Clint is working on a first draft to submit for review next week.

Full thread

Release Countdown for Week R-15, Jun 20-24

Focus:

Teams should be working on new feature development and bug fixes.

General Notes:

Members of the release team will be traveling next week. This will result in delays in releases. Plan accordingly.

Release Actions:

Official independent projects should file information about historical releases using the openstack/releases repository so the team pages on release.openstack.org are up to date.
Review stable/liberity and stable/mitaka branches for needed releases.

Important Dates:

Newton 2 milestone, July 14

Newton release schedule [2]

Full thread

Placement API WSGI Code – Let&8217;s Just Use Flask

Maybe it&8217;s better to use one of the WSGI frameworks used by the other OpenStack projects, instead of going in a completely new direction.

It will easier for other OpenStack contributors to become familiar with the new API placement API endpoint code if it uses Flask.
Flask has a very strong community and does stuff well that the OpenStack community could stop worrying about.

The amount of WSGI glue above Routes/Paste is pretty minimal in comparison to using a full web framework.

Template and session handling are things we don&8217;t need. We&8217;re a REST service, not web application.

Which frameworks are in use in Mitaka:

Falcon: 4 projects
Custom + routes: 12 projects
Pecan: 12 projects
Flask: 2 projects
web.py: 1 project

Full thread

[1] &8211; http://lists.openstack.org/pipermail/openstack-dev/2016-May/095452.html
[2] &8211; http://releases.openstack.org/newton/schedule.html
Quelle: openstack.org

da Agency

OpenStack turns 6: Community focuses on collaboration, growth

July 19 marks the 6th birthday of OpenStack, and we’re celebrating with the entire OpenStack community during July! OpenStack is an integration engine for diverse cloud technologies, fostering collaboration among emerging communities, and none of it would be possible without the quickly growing, global OpenStack community. There are now more than 54,000 community members, over 80 global user groups across 179 countries and more than 600 supporting companies. We think that deserves a worldwide celebration!

 
We’ve invited all our user groups to celebrate with us. This month, more than 45 OpenStack birthday parties will be thrown all over the world – celebrating the OpenStack community!  We encourage everyone to find a birthday party in your area and join your fellow community members to toast each other on another great year! Don’t forget to share your pictures and memories using #OpenStack6Bday.
Coming soon! Check out SuperuserTV&8217;s live interviews with user group coordinators around the word about how they are planning on celebrating Open Stack&8217;s 6th Birthday!
Find a local celebration in your area:
Argentina &8211; July 28
Atlanta, Georgia &8211; July 21
Baden-Württemberg, Germany &8211; TBD
Belgium &8211; July 5
Brazil &8211; July 16
Central Florida &8211; July 19
Colorado &8211; July 28
Durban &8211; July 8
Frankfurt, Germany &8211; TBD
Greece &8211; July 13
Guadalajara, Mexico &8211; July 15
Guatemala &8211; July 21
Hong Kong &8211; July 12
Italy &8211; July 18
Japan &8211; July 6-7
Kazan, Russia &8211; July 28
Kentucky &8211; July 28
Los Angeles &8211; July 28
Malaysia &8211; August 10
Manchester, UK &8211; July 27
Minnesota &8211; July 25
Morocco &8211; July 29
Munich &8211; July 19
Nairobi &8211; July 16
New York City &8211; July 13
Nigeria &8211; July 8
North Carolina &8211; July 21
Northern Virginia (NOVA) &8211; July 28
Pakistan &8211; July 27
Paris, France &8211; July 5
Philadelphia, Pennsylvania &8211; July 28
Romania &8211; July 14
Philippines &8211; July 22
San Francisco, California &8211; July 14**
South Korea &8211; July 21
St. Louis, Missouri &8211; July 21
Sweden &8211; July 6
Switzerland &8211; July 7
Thailand &8211; July 27-28 (tutorials); July 29 (launch party)
Toulouse, France &8211; July 4
Tunisia &8211; July 28
Turkey &8211; July 13
Vietnam &8211; July 30
Virginia &8211; July 18
Washington DC &8211; July 18
Quelle: openstack.org

da Agency

Get a high COA score. Win a Chromebook.

Are you ready to show off your OpenStack skills? The COA high score contest has begun! July 18th through September 11th, COA exam takers with the highest score each week will win a Chromebook from the OpenStack Foundation.
 
Entry is easy:

Go to openstack.org/coa and read the exam materials
Register and schedule your exam!

 
That’s it!
Winners will be notified via email. See the full contest rules below. Good luck!
 
Certified OpenStack Administrator Exam Contest
The Certified OpenStack Administrator Exam Contest (the “Contest”) is designed to encourage eligible individuals (&8220;Entrant(s)&8221; or &8220;You&8221;) to take the Certified OpenStack Administrator Exam (the “Exam”). OpenStack will choose the winner, and the prize will be awarded in accordance with these Official Rules (these &8220;Rules&8221;).

BINDING AGREEMENT: In order to enter the Contest, you must agree to the Rules. Therefore, please read these Rules prior to entry to ensure you understand and agree. You agree that submission of an entry in the Contest constitutes agreement to these Rules. You may not submit an entry to the Contest and are not eligible to receive the prize described in these Rules unless you agree to these Rules. These Rules form a binding legal agreement between you and OpenStack with respect to the Contest.
ELIGIBILITY: To be eligible to enter the Contest, an Entrant must be 18 years of age or older and eligible to take the Exam as set forth in the Exam Handbook (available for download on the Exam Website.  Contest is void where prohibited by law. Employees, directors, and officers of OpenStack and their immediate families (parents, siblings, children, spouses, and life partners of each, regardless of where they live) and members of the households (whether related or not) of such individuals are ineligible to participate in this Contest.
SPONSOR: The Contest is sponsored by OpenStack Foundation (&8220;OpenStack&8221; or &8220;Sponsor&8221;), a Delaware non-stock, non-profit corporation with principal place of business at 1214 West 6th Street, Suite 205 Texas, Austin, TX 78703, USA.
CONTEST PERIOD: The Contest begins on July 18, 2016 when posted to The OpenStack Blog (http://www.openstack.org/blog) and ends on September 11, 2016 11:59 Central Time (CT) Zone (&8220;Contest Period&8221;). All dates are subject to change.
HOW TO ENTER: To enter the Contest, visit the Exam website located at https://www.openstack.org/coa (&8220;Exam Website&8221;) during the Contest Period, click “Get Started,” and follow the prompts to purchase and take the Exam.  You will be automatically entered into the Contest by completing the Exam during the Contest Period.  If you start but do not complete the Exam during the Contest Period, you will not be entered into the Contest.  Additional entry information is available on The OpenStack Blog.  If you wish to opt out of the Contest, please email us at info@openstack.org. LIMIT ONE (1) ENTRY PER ENTRANT. Subsequent entries will be disqualified.
TAKING THE EXAM: To enter the Contest, you must complete the Exam.  You understand that in addition to these Rules, you must comply with all terms, conditions, rules, and requirements set by OpenStack and the Exam administrators for the Exam.  Information regarding the Exam is available on the Exam Website and in the Exam Handbook.
SCORING: Exams will be scored in accordance with the Exam Handbook, available for download on the Exam Website.  The winner will be the individual that achieves the highest score on the Exam. In the event of a tie, the individual who completed the Exam in the shortest amount of time will be the winner.  For the purposes of the tie-breaker, Exam time will be measured from initial commencement of the Exam to final submission.  Time from purchase of Exam to commencement of Exam will not be considered.
PRIZE: One winner will be selected.  The winner will receive a Toshiba Chromebook 2 – 2015 Edition (CB35-C3350) with an approximate retail value of $350 US Dollars.
TAXES: AWARD OF PRIZE TO POTENTIAL WINNER IS SUBJECT TO THE EXPRESS REQUIREMENT THAT THEY SUBMIT TO OPENSTACK ALL DOCUMENTATION REQUESTED BY OPENSTACK TO PERMIT IT TO COMPLY WITH ALL APPLICABLE STATE, FEDERAL AND LOCAL TAX REPORTING. TO THE EXTENT PERMITTED BY LAW, ALL TAXES IMPOSED ON PRIZES ARE THE SOLE RESPONSIBILITY OF THE WINNER. In order to receive a prize, potential winner must submit tax documentation requested by OpenStack or otherwise required by applicable law, to OpenStack or a representative for OpenStack or the relevant tax authority, all as determined by applicable law. The potential winner is responsible for ensuring that they comply with all the applicable tax laws and filing requirements. If the potential winner fails to provide such documentation or comply with such laws, the prize may be forfeited and OpenStack may, in its sole discretion, select an alternate potential winner.
GENERAL CONDITIONS: All federal, state and local laws and regulations apply. OpenStack reserves the right to disqualify any Entrant from the Contest if, in OpenStack’s sole discretion, it reasonably believes that the Entrant has attempted to undermine the legitimate operation of the Contest or Exam by cheating, deception, or other unfair playing practices or annoys, abuses, threatens or harasses any other entrants, or OpenStack. OpenStack retains all rights in the OpenStack products and services and entry into this Contest will in no case serve to transfer any OpenStack intellectual property rights to the Entrant.
PRIVACY: Entrants agree and acknowledge that personal data submitted with an entry, including name and email address may be collected, processed, stored and otherwise used by OpenStack for the purposes of conducting and administering the Contest. All personal information that is collected from Entrants is subject to OpenStack&8217;s Privacy Policy, located at http://www.openstack.org/privacy. Individuals submitting personal information in connection with the Contest have the right to request access, review, rectification or deletion of any personal data held by OpenStack in connection with the Contest by sending an email to OpenStack at info@openstack.org or writing to: Compliance Officer, OpenStack Foundation, P.O. Box 1903, Austin, TX 78767.
PUBLICITY: By entering the Contest, Entrants agree to participate in any media or promotional activity resulting from the Contest as reasonably requested by OpenStack at OpenStack&8217;s expense and agree and consent to use of their name and/or likeness by OpenStack. OpenStack will contact Entrants in advance of any OpenStack-sponsored media request.
WARRANTY AND INDEMNITY: Entrants warrant that they will take the Exam in compliance with all terms, conditions, rules, and requirements set forth on the Exam Website and in the Exam Handbook. To the maximum extent permitted by law, Entrant indemnifies and agrees to keep indemnified Sponsor at all times from and against any liability, claims, demands, losses, damages, costs and expenses resulting from any act, default or omission of the Entrant and/or a breach of any warranty set forth herein. To the maximum extent permitted by law, Entrant agrees to defend, indemnify and hold harmless Sponsor from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorney’s fees) arising out of or accruing from: (i) any misrepresentation made by Entrant in connection with the Contest or Exam; (ii) any non-compliance by Entrant with these Rules; (iii) claims brought by persons or entities other than the parties to these Rules arising from or related to Entrant&8217;s involvement with the Contest; (iv) acceptance, possession, misuse or use of any prize or participation in any Contest-related activity or participation in the Contest; (v) any malfunction or other problem with The OpenStack Blog or Exam Website in relation to the entry and participation in the Contest or completion of the Exam by Entrant; (vii) any error in the collection, processing, or retention of entry or voting information in relation to the entry and participation in the Contest or completion of the Exam by Entrant; or (viii) any typographical or other error in the printing, offering or announcement of any prize or winners in relation to the entry and participation in the Contest or completion of the Exam by Entrant.
ELIMINATION: Any false information provided within the context of the Contest by Entrant concerning identity, email address, or non-compliance with these Rules or the like may result in the immediate elimination of the entrant from the Contest.
INTERNET AND DISCLAIMER: OpenStack is not responsible for any malfunction of The OpenStack Blog or Exam Website or any late, incomplete, or mis-graded Exams due to system errors, hardware or software failures of any kind, lost or unavailable network connections, typographical or system/human errors and failures, technical malfunction(s) of any network, cable connections, satellite transmissions, servers or providers, or computer equipment, traffic congestion on the Internet or at The OpenStack Blog or Exam Website, or any combination thereof. OpenStack is not responsible for the policies, actions, or inactions of others, which might prevent Entrant from entering, participating, and/or claiming a prize in this Contest. Sponsor&8217;s failure to enforce any term of these Rules will not constitute a waiver of that or any other provision. Sponsor reserves the right to disqualify Entrants who violate the Rules or interfere with this Contest in any manner. If an Entrant is disqualified, Sponsor reserves the right to terminate that Entrant&8217;s eligibility to participate in the Contest.
RIGHT TO CANCEL, MODIFY OR DISQUALIFY: If for any reason the Contest is not capable of running as planned, OpenStack reserves the right at its sole discretion to cancel, terminate, modify or suspend the Contest. OpenStack further reserves the right to disqualify any Entrant who tampers with the Exam process or any other part of the Contest, Exam, The OpenStack Blog, or Exam Website. Any attempt by an Entrant to deliberately damage any web site, including the The OpenStack Blog or Exam Website, or undermine the legitimate operation of the Contest or Exam is a violation of criminal and civil laws and should such an attempt be made, OpenStack reserves the right to seek damages from any such Entrant to the fullest extent of the applicable law.
FORUM AND RECOURSE TO JUDICIAL PROCEDURES: These Rules shall be governed by, subject to, and construed in accordance with the laws of the State of Texas, United States of America, excluding all conflict of law rules. If any provision(s) of these Rules are held to be invalid or unenforceable, all remaining provisions hereof will remain in full force and effect. Exclusive venue for all disputes arising out of the Rules shall be brought in the state or federal courts of Travis County, Texas, USA and you agree not to bring an action in any other venue. To the extent permitted by law, the rights to litigate, seek injunctive relief or make any other recourse to judicial or any other procedure in case of disputes or claims resulting from or in connection with this Contest are hereby excluded, and Entrants expressly waive any and all such rights.
WINNER&8217;S LIST: The winner will be announced on The OpenStack Blog.  You may also request a list of winners after December 1, 2016 by sending a self-addressed stamped envelope to:

OpenStack Inc.
Attn: Contest Administrator
P.O. Box 1903
Austin, Texas 78767
(Residents of Vermont need not supply postage).
 
Quelle: openstack.org

da Agency

OpenStack Developer Mailing List Digest July 2-22

SuccessBot Says

Notmyname: the 1.5 year long effort to get at-rest encryption in openstack swift has been finished. at-rest crypto has landed in master
stevemar: API reference documentation now shows keystone’s in-tree APIs!
Samueldemq: Keystone now supports Python 3.5
All

Troubleshooting and ask.openstack.org

Keystone team wants to do troubleshooting documents.
Ask.openstack.org might be the right forum for this, but help is needed:

Keystone core should be able to moderate.
A top level interface than just tags. The page should have a series of questions and links to the discussions for that question.

There could also be a keystone-docs repo that would have:

FAQ troubleshooting
Install guides
Unofficial blog posts
How-to guides

We don&8217;t want a static troubleshooting guide. We want people to be able to ask questions and link them to answers.
Full thread

Leadership Training Recap and Steps Forward

Colette Alexander has successfully organized leadership training in Ann Arbor, Michigan.
17 people from the community attended. 8 of them from the TC.
Subjects:

servant leadership
Visioning
Stages of learning
Good practices for leading organizational change.

Reviews and reflections from the training have been overwhelmingly positive and some blogs started to pop up [1].
A smaller group of the 17 people after training met to discuss how some ideas presented might help the OpenStack community.

To more clearly define and accomplish that work, a stewardship working group has been proposed [2].

Because of the success, and 5 TC members weren&8217;t able to attend, Colette is working to arrange a repeating offer.
Thanks to all who attended and the OpenStack Foundation who sponsored the training for everyone.
Full thread

Release Countdown For Week R-12, July 11-15

Focus:

Major feature work should be well under way as we approach the second milestone.

General notes:

We freeze release libraries between the third milestone and final release.

Only emergency bug fix updates are allowed during that period.
Prioritize any feature work that includes work in libraries.

Release actions:

Official projects following any of the cycle-based release models should propose beta 2 tags for their deliverables by July 14.
Review stable/liberty stable/mitaka branches for needed releases.

Important dates:

Newton 2 milestone: July 14
Library release freeze date starting R-6, Aug 25
Newton 3 milestone: September 1

Full thread

The Future of OpenStack Documentation

Current central documentation

Consistent structure
For operators and users
Some less technical audience use this to evaluate with various other cloud infrastructure offerings.

Project documentation trends today:

Few are contributing to central documentation
More are becoming independent with their own repository documentation.
An alarming number just don&8217;t do any.

A potential solution: Move operator and user documentation into individual project repositories:

Project developers can contribute code and documentation in the same patch.
Project developers can work directly or with a liaison documentation team members to improve documentation during development.
The documentation team primarily focuses on organization/presentation of documentation and assisting projects.

Full thread

 
[1] – http://www.tesora.com/openstack-tc-will-not-opening-deli/
[2] &8211; https://review.openstack.org/#/c/337895/
 
Quelle: openstack.org