8217 News, Entwicklungen, Updates, HowTos - Seite 26 von 31

The post What’s the big deal about running OpenStack in containers? appeared first on Mirantis | The Pure Play OpenStack Company.
Ever since containers began their meteoric rise in the technical consciousness, people have been wondering what it would mean for OpenStack. Some of the predictions were dire (that OpenStack would cease to be relevant), some were more practical (that containers are not mini VMs, and anyway, they need resources to run on, and OpenStack still existed to manage those resources).
But there were a few people who realized that there was yet another possibility: that containers could actually save OpenStack.
Look, it&8217;s no secret that deploying and managing OpenStack is difficult at best, and frustratingly impossible at worst. So what if I told you that using Kubernetes and containers could make it easy?
Mirantis has been experimenting with container-based OpenStack for the past several years — since before it was “cool” &8212; and lately we&8217;d decided on an architecture that would enable us to take advantage of the management capabilities and scalability that comes with the Kubernetes container orchestration engine. (You might have seen the news that we&8217;ve also acquired TCP Cloud, which will help us jump our R&D forward about 9 months.)
Specifically, using Kubernetes as an OpenStack underlay lets us turn a monolithic software package into discrete services with well-defined APIs that can be freely distributed, orchestrated, recovered, upgraded and replaced &8212; often automatically based on configured business logic.
That said, it&8217;s more than just dropping OpenStack into containers, and talk is cheap. It&8217;s one thing for me to say that Kubernetes makes it easy to deploy OpenStack services. And frankly, almost anything would be easier than deploying, say, a new controller with today&8217;s systems.
But what if I told you you could turn an empty bare metal node into an OpenStack controller just by adding a couple of tags to it?
Have a look at this video (you&8217;ll have to drop your information in the form, but it just takes a second):
Containerizing the OpenStack Control Plane on Kubernetes: auto-scaling OpenStack services
I know, right? Are you as excited about this as I am?
The post What&8217;s the big deal about running OpenStack in containers? appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis

28. September 201628. September 2016

da Agency

Let’s meet in Barcelona at the OpenStack Summit!

The post Let’s meet in Barcelona at the OpenStack Summit! appeared first on Mirantis | The Pure Play OpenStack Company.

As we count down the days to the OpenStack Summit in Barcelona on October 24-28, we’re getting ready to share memorable experiences, knowledge, and fun!

Come to booth C27 to see what we’ve built with OpenStack, and join in an “Easter Egg Hunt” that will test your observational skills and knowledge of OpenStack, Containers, and Mirantis swag from prior summits. If you find enough Easter eggs, you&8217;re entered in our prize drawing for a $300 Visa gift card or an OpenStack certification exam from our OpenStack Training team ($400 value). And as always, we’re giving away more awesome swag you’ve come to expect from us.

If you&8217;d like to set up some time at the summit to talk with our team, simply contact us and we&8217;ll schedule a meeting.

REQUEST A MEETING

Free Training
Mirantis is also providing two FREE training courses based on our standard industry-leading curriculum. If you&8217;re interested in attending, please follow the links below to register:

Tuesday, October 25th: OpenStack Fundamentals
Wednesday, October 26th: Introduction to Kubernetes & Docker

Mirantis Presentations
Here&8217;s where you can find us during the summit….
TUESDAY OCTOBER 25

Tuesday, 12:15pm-12:55pm
Level: Intermediate
Chasing 1000 nodes scale
(Dina Belova and Alex Shaposhnikov, Mirantis; Inria)

Tuesday, 12:15pm-12:55pm
Level: Intermediate
OpenStack: you can take it to the bank!
(Ivan Krovyakov, Mirantis; Sberbank)

Tuesday, 3:05pm-3:45pm
Level: Intermediate
Live From Oslo
(Oleksii Zamiatin, Mirantis; EasyStack, Red Hat, HP)

Tuesday, 3:55pm-4:35pm
Level: Intermediate
Is your cloud forecast a bit foggy?
(Oleksii Zamiatin, Mirantis; EasyStack, Red Hat, HP)

Tuesday, 5:05pm-5:45pm
Level: Intermediate
Kerberos and Health Checks and Bare Metal, Oh My! Updates to OpenStack Sahara in Newton.
(Nikita Konovalov and Vitaly Gridnev, Mirantis; Red Hat)

WEDNESDAY OCTOBER 26

Wednesday, 11:25am-12:05pm
Level: Intermediate
The race conditions of Neutron L3 HA&8217;s scheduler under scale performance
(Ann Taraday and Kevin Benton, Mirantis; Red Hat)

Wednesday, 11:25am-12:05pm
Level: Advanced
The race conditions of Neutron L3 HA&8217;s scheduler under scale performance
(Florin Stingaciu and Shaun O&8217;Meara, Mirantis)

Wednesday, 12:15pm-12:55pm
Level: Beginner
The Good, Bad and Ugly: OpenStack Consumption Models
(Amar Kapadia, Mirantis; IDC, EMC, Canonical)

Wednesday, 12:15pm-12:55pm
Level: Intermediate
OpenStack Journey in Tieto Elastic Cloud
(Jakub Pavlík, Mirantis TCP Cloud; Tieto)

Wednesday, 2:15pm-3:45pm
Level: Intermediate
User Committee Session
(Hana Sulcova, Mirantis TCP Cloud; Comcast, Workday, MIT)

Wednesday, 3:55pm-4:35pm
Level: Beginner
Lessons from the Community: What I&8217;ve Learned As An OpenStack Day Organizer
(Hana Sulcova, Mirantis TCP Cloud; Tesora, GigaSpaces, CloudDon, Intel, Huawei)

Wednesday, 3:05pm-3:45pm
Level: Beginner
Glare – a unified binary repository for OpenStack
(Mike Fedosin and Kairat Kushaev, Mirantis)

Wednesday, 3:55pm-4:30pm
Level: Intermediate
OpenStack Requirements : What we are doing, what to expect and whats next
(Davanum Srinivas, Mirantis; RedHat)

Wednesday, 3:55pm-4:35pm
Level: Intermediate
Is OpenStack Neutron production ready for large scale deployments?
(Oleg Bondarev, Satish Salagame and Elena Ezhova, Mirantis)

Wednesday, 5:05pm-5:45pm
Level: Beginner
How Four Superusers Measure the Business Value of their OpenStack Cloud
(Kamesh Pemmaraju and Amar Kapadia, Mirantis)

THURSDAY OCTOBER 27

Thursday, 9:00am-9:40am
Level: Intermediate
Sleep Better at Night: OpenStack Cloud Auto-Healing
(Mykyta Gubenko and Alexander Sakhnov, Mirantis)

Thursday, 11:00am-11:40am
Level: Advanced
OpenStack on Kubernetes &8211; Lessons learned
(Sergey Lukjanova, Mirantis; Intel, CoreOS)

Thursday, 11:00am-11:40am
Level: Intermediate
Unified networking for VMs and containers for Openstack and k8s using Calico and OVS
(Vladimir Eremin, Mirantis; Intel)

Thursday, 11:50am-12:30pm
Level: Intermediate
Kubernetes SDN Performance and Architecture Evaluation at Scale
(Jakub Pavlík and Marek Celoud, Mirantis TCP Cloud)

Thursday, 3:30pm-4:10pm
Level: Advanced
Ironic Grenade: Blowing up our upgrades.
(Vasyl Saienko, Mirantis; Intel)

Thursday, 3:30pm-4:10pm
Level: Beginner
Application Catalogs: understanding Glare, Murano and Community App Catalog
(Alexander Tivelkov and Kirill Zaitsev, Mirantis)

Thursday, 5:30pm-6:10pm
Level: Beginner
What&8217;s new in OpenStack File Share Services (Manila)
(Gregory Elkinbard, Mirantis; NetApp)
The post Let’s meet in Barcelona at the OpenStack Summit! appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis

24. September 201624. September 2016

da Agency

OpenStack Developer Mailing List Digest September 17-23

Announcing firehose.openstack.org

A MQTT based unified message bus for infra services.
This allows a single place to go for consuming messages of events from infra services.
Two interfaces for subscribing to topics:

MQTT protocol on the default port
Websockets over port 80

Launchpad and gerrit events are the only things currently sending message to firehose, but the plan is to expand this.
An example [1] of gerritbot on the consuming side, which has support for subscribing to gerrit event stream over MQTT.
A spec giving details on firehose [2].
Docs on firehose [3].

Full thread

Release countdown for week R-1, 26-30

Focus: All teams should be working on release-critical bugs befor ethe final release.
General

29th September is the deadline for the new release candidates or release from intermediary projects.
Quiet period to follow before the last release candidates on 6th October.

Release actions:

Projects not following the milestone-based release model who want a stable/newton branch created should talk to the release team.
Watch for translation patches and merge them quickly to ensure we have as many user-facing strings translated as possible in the release candidates.

If your project has already been branched, make sure those patches are applied to the stable branch.

Liaisons for projects with independent deliverables should import the release history by preparing patches to openstack/release.

Important Dates:

Newton last RC, 29 September
Newton final release, 6 October
Newton release schedule [4]

Full thread

Removal of Security and OpenStackSalt Project Teams From the Big Tent

The Security and OpenStackSalt projects are without PTLs. Projects leaderless default to the #Technical Committee for decision of what to do with the project [5]. Majority of the Technical Committee has agreed to have these projects removed.
OpenStackSalt is a relatively new addition to the Big Tent, so if they got their act together, they could be reproposed.
We still need to care about security., and we still need a home for the vulnerability management team (VMT). The suggested way forward is to have the VMT apply to be its own official project team, and have security be a working group.
The Mitaka PTL for the Security mentions missing the election date, but provides some things the team has been working on:

Issuing Security Notes for Glance, Nova, Horizon, Bandit, Neutron and Barbican.
Updating the security guide (the book we wrote on securing OpenStack)
Hosting a midcycle and inducting new members
Supporting the VMT with several embargoed and complex vulnerabilities
Building up a security blog
Making OpenStack the biggest open source project to ever receive the Core
Infrastructure Initative Best Practices Badge
Working on the OpenStack Security Whitepaper
Developing CI security tooling such as Bandit

One of the Technical Committee members privately received information that explains why the security PTL was not on top of things. With ~60 teams around there will always be one of two that miss, but here we’re not sure it passes the bar of “non-alignment with the community” that would make the security team unfit to be an official OpenStack Team.
Full thread

[1] – http://git.openstack.org/cgit/openstack-infra/gerritbot/commit/?id=7c6e57983d499b16b3fabb864cf3b
[2] &8211; http://specs.openstack.org/openstack-infra/infra-specs/specs/firehose.html
[3] &8211; http://docs.openstack.org/infra/system-config/firehose.html
[4] &8211; http://releases.openstack.org/newton/schedule.html
[5] &8211; http://docs.openstack.org/project-team-guide/open-community.html#technical-committee-and-ptl-elections
Quelle: openstack.org

23. September 201623. September 2016

da Agency

5 Minutes with the Docker Captains

#Docker Captain is a distinction that Docker awards select members of the community that are both experts in their field and are passionate about sharing their Docker knowledge with others.

This week we are highlighting 3 of our outstanding Captains who are making September one filled with Docker learnings and events. Read on to learn more about how they got started, what they love most about Docker, and why Docker.
Alex Ellis
Alex is a Principal Application Developer with expertise in the full Microsoft .NET stack, Node.js and Ruby. He enjoys making robots and IoT-connected projects with Linux and the Raspberry PI microcomputer. He is a writer for Linux User and Developer magazine and also produces tutorials on Docker, coding and IoT for his tech blog at alexellis.io.

As a Docker Captain, how do you share that learning with the community?
I started out by sharing tutorials and code on my blog alexellis.io and on Github. More recently I’ve attended local meet-up groups, conferences and tech events to speak and tell a story about Docker and cool hacks. I joined Twitter in March and it’s definitely a must-have for reaching people.
Why do you like Docker?
Docker makes the complex seem simple and forces you to automate your workflow. I have a background in software engineering and automation is everything for delivering reliable, repeatable and testable systems.
What’s a common tech question you’re asked and the high-level explanation?
The questions vary and often surprise me – I like to be able to connect people to the right Captains or Docker folks. Opening an issue about a technical problem on Github is really valuable for the community and the Docker project. Please give feedback.
What’s your favorite thing about the Docker community?
The community is vibrant and full of life &8211; people are working on solutions for problems that you may have and are generous with their knowledge.
Who are you when you’re not online?
I love film photography &8211; everything from buying vintage cameras, to developing and printing my own images. I balance my time at the screen with road cycling &8211; cruising down country lanes in the countryside or spending just time away from the screen in the great outdoors.
Marcos Lilljedahl
Marcos Lilljedahl is an OS evangelist and Golang lover with a strong background in distributed systems and app architecture. Marcos is currently working at Matica, a Machine Learning startup that brings latest in research to industry. Mantica runs Machine learning apps in a fully dockerized environment mainly using compose / machine and engine.

How has Docker impacted what you do on a daily basis?
Although I run pretty much everything in containers (even games like Counter Strike / Quake3 / etc), the biggest benefit comes from the fact that it really has helped to reduce friction when working with different teams and platforms. It’s a fundamental tool for everyone to speak the same “app” language and then translate that directly into production.
As a Docker Captain, how do you share that learning with the community?
I’m not the “blog post” kind of person, I usually like to deep dive into code and understand the core principles about Docker. I usually contribute by helping people resolve GitHub issues or by responding on the Slack community channel when there are specific questions or unexpected issues. Also, whenever I find some time, I like to hack on stuff like our two hackathon winner projects CMT and Whaleprint.
Why do you like Docker?
What I like the most is its fundamental purpose (help people with great ideas to make things possible) and the community behind it.
Who are you when you’re not online?
I like to do all kind of sports like sailing, swimming, playing soccer, running, snowboarding, roller hockey and crossfit. I also enjoy spending weekends with my girlfriend and family cooking asado.
If you could meet anyone in the world dead or alive who would it be and why?
I would have loved to meet young Steve Jobs. I believe he transmitted the energy to make anyone do the impossible.
Sreenivas Makam
Sreenivas Makam is currently working as a senior engineering manager at Cisco Systems, Bangalore. His interests include SDN, NFV, Network Automation, DevOps, and cloud technologies, and he likes to try out and follow open source projects in these areas. His blog can be found at sreeninet.wordpress.com and his hacky code at github.com/smakam. Sreenivas wrote a book on Mastering CoreOS, which was published in February 2016. He has done the technical reviewing for Mastering Ansible book, Packt Publishing, Ansible Networking Report, O’Reilly Publisher and Network programmability and Automation book, O&8217;Reilly Publisher. He has given presentations at Docker and other meetups in Bangalore.

How has Docker impacted what you do on a daily basis?
I come from a networking background and used to approach problems from an infrastructure point of view. Docker has given me the insight to approach problems from a developer or an operator perspective.
As a Docker Captain, how do you share that learning with the community?
I enjoy sharing my learning and knowledge through my blogs. Other than this, I give presentations in Docker meetups and other meetups in Bangalore. The best part about being a Docker captain is the direct access to Docker developers and other Docker captains and there is always something new to learn from them.
How did you first get involved with Docker?
I was fascinated with cloud adoption and trying out related technologies like AWS and Google cloud, Openstack and SDN. I dabbled into Docker as part of this. I was initially impressed with how fast I could build, deploy and destroy a Docker container. I got involved in Docker from October 2014 and the first version I used was Docker 1.3.
Why do you like Docker?
There are many reasons, the biggest reason is perhaps the simplicity. There has been a lot of effort put in making complex topics like Orchestration and Security very easy to use for both developers and operations teams.
What’s your favorite thing about the Docker community?
The Docker community is super-active, encourages new members and supports diversity.
Follow all of the Docker Captains on Twitter using Docker with Alex Ellis’ tutorial.
Docker Captains
Captains are Docker ambassadors (not Docker employees) and their genuine love of all things Docker has a huge impact on the Docker community – whether they are blogging, writing books, speaking, running workshops, creating tutorials and classes, offering support in forums, or organizing and contributing to local events – they make Docker’s mission of democratizing technology possible. Whether you are new to Docker or have been a part of the community for a while, please don’t hesitate to reach out to Docker Captains with your challenges, questions, speaking requests and more.
While Docker does not accept applications for the Captains program, we are always on the lookout to add additional leaders that inspire and educate the Docker community. If you are interested in becoming a Docker Captain, we need to know how you are giving back. Sign up for community.docker.com, share your activities on social media with the Docker, get involved in a local meetup as a speaker or organizer and continue to share your knowledge of Docker in your community.
The post 5 Minutes with the Docker Captains appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

17. September 201617. September 2016

da Agency

OpenStack Developer Mailing List Digest September 10-16

Nominations for OpenStack PTLs Are Now Open

Will remain open until September 18 23:45 UTC
Submit a text file to the openstack/election repository [1].

File name convention: $cycle_name/$project_name/$ircname.txt

In order to be an elgible candidate (and be allowed to vote) you need to have contributed an accepted patch to one of the program projects during the Mitaka-Newton timeframe.
Additional information [2].
Approved candidates [3]
Elections will start at September 19, 2016 00:00 UTC until September 25 23:45 UTC
Full thread

#Ocata Design Summit – Proposed Slot Allocation

Proposed slot allocation for project teams at the Ocata design summit in Barcelona [4] based on requests current PTLs have made and adjusted for limit space available.
Kendall Nelson and Thierry will start laying out those sessions over the available rooms and time slots.
Communicated constraints (e.g. Manila not wanting to overlap with Cinder) should be communicated to Thierry asap.
If you don’t plan to use all of your slots, let Thierry know so they can be given to a team that needs them.
Start working with your team on content you&8217;d like to cover at the summit and warm up those etherpads!
Full thread

OpenStack Principles

A set of OpenStack principles is proposed [5] to accurately capture existing tribal knowledge as a prerequisite for being able to have an open and productive discussions about changing it.
Last time majority of the Technical Committee were together, it was realized that there were a set of unspoken assumptions carried and used to judge things.

These are being captured to empower everyone to actually be able challenge and discuss them.

The principles were started by various TC members who have governance history and know these principles. This was in attempt to document this history to commonly asked questions. These are not by any means final, and the community should participate in discussing them.
Full thread

API Working Group News

Recently merged guidelines

URIs [6]
Links [7]
Version string being parsable [8]

Guidelines Under review

Add a warning about JSON expectations. [9]

Full thread

[1] – http://governance.openstack.org/election/#how-to-submit-your-candidacy
[2] &8211; https://governance.openstack.org/election/
[3] &8211; http://governance.openstack.org/election/ocata-ptl-candidates
[4] &8211; http://lists.openstack.org/pipermail/openstack-dev/2016-September/103560.html
[5] &8211; https://review.openstack.org/#/c/357260/5
[6] &8211; https://review.openstack.org/322194
[7] &8211; https://review.openstack.org/354266
[8] &8211; https://review.openstack.org/346846
[9] &8211; https://review.openstack.org/#/c/364460/

Quelle: openstack.org

16. September 201616. September 2016

da Agency

Install your OpenStack Cloud before lunchtime

Figure 1. The inner workings of QuickStart Cloud Installer
What if I told you that you can have your OpenStack Cloud environment setup before you have to stop for lunch?
Would you be surprised?
Could you do that today?
In most cases I am betting your answer would be not possible, not even on your best day. Not to worry, a solution is here and it’s called the QuickStart Cloud Installer (QCI).
Let&8217;s take a look at the background of where this Cloud tool came from, how it evolved and where it is headed.

Born from need
As products like Red Hat Cloud Suite emerge onto the technology scene, it exemplifies the need for companies to be able to support infrastructure and application development use cases such as the following:

Optimize IT
Accelerate Service Delivery
Modernize Development and Operations
Scalable Infrastructure

The problem is how to streamline the setup of such intricate and complex solutions?
Figure 2. Getting the installation of complex infrastructure solutions down from a month, to days, to just hours based on testing by Red Hat.
It started with researching in 2013 how the product Red Hat Cloud Infrastructure (RHCI) was being deployed by Red Hat customers. That information was used to start an effort creating several simple, reproducible installation guides that could cut down the time needed to install the following products.

Red Hat Virtualization (RHV)
OpenStack Platform (OSP)
CloudForms

The final product installation documentation brought the deployment time for this infrastructure solution down to just several days, instead of a month. Figure 2 shows the progress made between the efforts of installing RHCI.
The next evolution included Satellite and OpenShift offerings that you now find in the Red Hat Cloud Suite solution. This brought more complexity into the installation process and a push was made to go beyond just documentation. An installation effort commenced that had to bring together all the products, deal with their configurations and manage it all to a full deployment in a faster time frame than several days.

How it works
The QCI progressed and expanded by functioning as an extension (plugin) of Satellite with intentional roadmap alignment. It uses specific product plugins that interface with their individual APIs so that they can be used for both individual product installations and complete solution base installs.
Figure 1 shows you the architectural layout of QCI as it relates to Satellite. See the online documentation for the versions supported by QCI at the time of this writing, we expect to update the documentation on a regular basis as products are released that QCI supports.
The installer, when first started, spins up the Fusor Installer. This is a plugin to Foreman and is used to perform the initial setup such as networking and provisioning within Satellite to be used later in the deployment.
Some of the deployment steps depend on the path you have chosen when specifying the products you wish to install:

if a RHV with CloudForms deployment is chosen, the QCI calls Puppet modules for configuring and setting up the RHV environment. It installs RHV-M and runs Python scripts which will set the RHV Datacenter up.
CloudForms management engine is deployed as a Satellite resource and as such can be launched on top of RHV.
Most of the OpenShift product deployment uses Ansible to facilitate the installation and setup of the environment.
OpenStack uses what is known as the TripleO installation. This means OpenStack installed on OpenStack (hence the three O&8217;s). It uses an all-in-one ISO image containing OpenStack which then deploys a customized version configured through QCI user interface.

The two deployment patterns supported by QCI are:

Red Hat Cloud Infrastructure

Satellite, RHV, OpenStack and CloudForms

Red Hat Cloud Suite

Satellite, RHV, OpenStack, CloudForms and OpenShift product

Now here is the unbelievable part we suggested in the title, that both deployment patterns can be installed in under four hours.
Figure 3. The timeline from pushing the deploy button to completion of your OpenStack deployment.
Yes, you can arrive in the morning to work and have your OpenStack Cloud infrastructure setup by the time you have to break for lunch!
Figure 3 shows you a condensed timeline of our testing of the RHCI installation as an example, but the same is possible with Red Hat Cloud Suite.

The future is bright
We can&8217;t think of anything brighter for you than a future where you can reduce deployment times for your complex Cloud infrastructure, but there are more positive points to take note of when you leverage QCI:

Simple fully integrated deployments of RHCI and Red Hat Cloud Suite requiring only minimal documentation.
Easy to use, single graphical web-based user interface for deploying all products.
Leverages existing Red Hat Storage (Ceph and Gluster) deployments for Red Hat Virtualization, Red Hat OpenStack, and OpenShift product installations.
Integrated with Red Hat’s Customer Portal for automated subscription management.
Avoid the need for costly consultants when deploying proof-of-concept environments.

With this in mind the team behind this technology is busy looking at expanding into more products and solutions within the Red Hat portfolio. Who knows, maybe the next step could be including partner technologies or other third-party solutions?

No time like the present for you to dive right and take QCI for a spin and be sure to let us know what you think of it.

(This article written together with Red Hat Software Engineer Nenad Peric)
Quelle: RedHat Stack

I was poking around Facebook’s privacy settings – when I accidentally discovered the site’s ad preferences page.

In my case, that includes blankets and carbohydrates which is *pretty* accurate, tbh.

“Slide to unlock” doesn’t exist anymore. You now have to press the home button twice with Touch ID or once to enter in a passcode – but there’s a workaround.

From the lock screen, access the camera by swiping left (instead of up).

In my case, that includes blankets and carbohydrates which is pretty accurate, tbh.