April 2017 - Seite 113 von 178 - Cloud Computing Köln

The post A whirlwind tour of open cloud trends in China with UMCloud appeared first on Mirantis | Pure Play Open Cloud.
Recently I had the pleasure of making my first visit to China to visit Mirantis’ partner, UMCloud. Along with Greg Elkinbard, Mirantis’ senior technical director for NFV technologies, we visited Beijing, Suzhou (a gem of a city I was not familiar with before), and Shanghai.
Over the course of the week we visited with several large firms that have or are planning some significant OpenStack deployments. Several trends caught my attention.

Open platforms resonate in this market. The phrases “pure play” and “no vendor lock-in” are tangible considerations for many of the firms we spoke with. These firms want an open platform that lets them work with many partners and adapt to changing conditions. Many deployments will include multiple options for SDN or other components as a way to future-proof the deployment. This trend is reflected in the strong participation in communities like OpenStack, OPNFV, and ONAP by Chinese firms.

These clouds are big. We talked to several firms who are planning or already running clouds of several hundred or even a few thousand nodes. These operators have made big clouds work after significant investment, and now they’re looking to standardize and improve the operational aspects.

These clouds are broad. The big clouds are not dedicated to a single vertical such as service providers or media providers. While these are represented, we also heard from firms that are running big clouds for general IT workloads. There’s also significant interest in Big Data and IoT workloads.

OpenStack has a healthy ecosystem in China. The strong demand for OpenStack has spurred a healthy crop of OpenStack-focused companies.

Finally, many thanks to our colleagues at UMCloud for all of their hospitality. Until next time!
The post A whirlwind tour of open cloud trends in China with UMCloud appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

12. April 201712. April 2017

da Agency

Announcing Azure SDK for Node.js 2.0 preview

Today we're excited to announce the 2.0 preview of the Azure SDK for Node.js. This update is packed with features to help you be more productive and we&039;ve added 20 new modules for services such as SQL and DocumentDB management.

As usage of the Azure SDK for Node.js continues to grow, we&039;ve received a lot of feedback from the community on how the SDK helps Node.js developers build on Azure and how some changes could make them more productive. With that feedback in mind, we set out to make some significant improvements to the developer experience, which includes enhancements to the modules themselves as well as some updates to make working in Visual Studio Code better.

Keep in mind that, as this is a preview release, it&039;s incredibly important to share your feedback with us on any issues or delightful experiences you face. Please open an issue on GitHub or connect with us directly on the Azure Developers Slack team with any questions or feedback.

Promises

With the way the module is being used, we&039;ve seen a lot of opportunities to improve the code that people are writing and maintaining.

This also makes it possible to use async and await in TypeScript or ES2017 environments.

Updated typings

Visual Studio Code&039;s rich Intellisense support makes building apps much quicker and more intuitive. Building with the Azure SDK is no exception and the typings have been updated and improved to provide you with the best possible experience.

New modules

Aside from the updates to the existing modules, this update includes the preview release of 20 new modules.

Advisor Management (azure-arm-advisor)
Automation Management (azure-arm-automation)
Billing Management (azure-arm-billing)
Cognitive Services Management (azure-arm-cognitiveservices)
Container Registry Management (azure-arm-containerregistry)
Customer Insights Management (azure-arm-customerinsights)
DocumentDB Management (azure-arm-documentdb)
Logic Management (azure-arm-logic)
Machine Learning Management (azure-arm-machinelearning)
Media Services Management (azure-arm-mediaservices)
Operational Insights Management (azure-arm-operationalinsights)
Recovery Services Backup Management (azure-arm-recoveryservicesbackup)
Recovery Services Management (azure-arm-recoveryservices)
Relay Management (azure-arm-relay)
Scheduler Management (azure-arm-scheduler)
Search Management (azure-arm-search)
ServiceFabric Management (azure-arm-servicefabric)
ServiceMap Management (azure-arm-servicemap)
SQL Management (azure-arm-sql)
Storage Import Export Management (azure-arm-storageimportexport)

Moving to the preview

Migrating to the preview is low in complexity and should be a direct replacement without changes to your code. When migrating to the preview it&039;s important to note that because of new implementation, using ES6 features, Node.js version 6.x is required. All of the existing callback-based methods will continue to work; however, omitting the final parameter will result in the method returning a promise.

Sending custom requests

With new updates to the runtime ms-rest and ms-rest-azure, you can make generic requests to Azure with the authenticated client. This is useful when debugging an issue or for making custom requests to the Azure API.

The following example makes a custom, long running request to get all resource groups in a subscriptions then writes the result to standard out. Detailed documentation is available on GitHub.

const msrest = require(&039;ms-rest&039;);
const msRestAzure = require(&039;ms-rest-azure&039;);

const clientId = process.env[&039;CLIENT_ID&039;];
const secret = process.env[&039;APPLICATION_SECRET&039;];
const domain = process.env[&039;DOMAIN&039;]; // Also known as tenantId.
const subscriptionId = process.env[&039;AZURE_SUBSCRIPTION_ID&039;];

msRestAzure.loginWithServicePrincipalSecret(clientId, secret, domain).then((creds) => {
let client = new msRestAzure.AzureServiceClient(creds);

return client.sendLongRunningRequest(options);
})
.then(console.dir.bind(console))
.catch(console.error.bind(console));
Quelle: Azure

12. April 201712. April 2017

da Agency

DockerCon Agenda, Mobile App and DockerCon Slack

From Docker use cases at large corporations, to advanced technical talks and hands-on lab tutorials, the #DockerCon Agenda includes sessions adapted to every attendee profile, expertise level and domain of interest.
If you’re a registered attendee, login on the DockerCon portal using the information you set up during the registration process. You can use the keyword search bar or filter by topics, days, tracks, experience level or target audience.

Once logged in, you can “star” your interests and create your DockerCon schedule. Your saved interests and schedule will be available on the DockerCon mobile app you can download here.
Below are some useful tips and tricks for getting the most out of the DockerCon App.
Add More Sessions in the App
If you have not started already, we encourage you to review DockerCon sessions and build your agenda for next week. The process is very simple and will help you organize sessions and activities by the topics that you are interested in. Just click the “Schedule” widget and explore sessions by day or track. When you add to “My Agenda”, you’ll be able to it find later in “My Event”.
You can use the DockerCon App to take notes and rate both speakers and sessions. You can also access your Moby Mingle account to submit offers or join requests allowing you to connect with other attendees. Just log in once using your registration credentials and then it will be saved for the week.
The Mapping section includes a map of the Ecosystem Expo Hall giving you the details of where you can find sponsor’s booths.
#DockerSelfie
Don’t forget to post your DockerSelfie photos to the Photo Feed! What’s a DockerSelfie? It’s just a selfie-style picture that features something Docker-related. Share pics with your Docker swag, at DockerCon or from other Docker events. Let us know how excited you are for DockerCon.
Introducing a DockerCon Slack
We’ve set up a DockerCon slack so that it’s easier for attendees to participate in topic-based conversations in specific channels. This is a great way to interact with attendees online and ask questions to the Docker team who will be looking after the different channels. As always, please remember that this is a professional event and it’s important to adhere to the Code of Conduct.

Time to build your @dockercon agenda and download the dockercon App Click To Tweet

The post DockerCon Agenda, Mobile App and DockerCon Slack appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

12. April 201712. April 2017

da Agency

Docker Docs Hackathon: April 17-21, 2017

During DockerCon 2017, #Docker’s #docs team will be running the first-ever Docker Docs hackathon, and you’re invited to participate and win prizes – whether you attend DockerCon or are just watching the proceedings online.
Essentially, it’s a bug-bash! We have a number of bugs filed against our docs up on GitHub for you to grab.
You can participate in one of two ways:

With the docs team’s help in the fourth floor hack room at DockerCon on Tuesday, April 18th and Wednesday, April 19th, from 1-6pm.
Online! Right here! During the whole week of DockerCon (April 17th – 21st).

Or, both – if you want to have the best shot. After all, we won’t be in the hack room 24/7 that whole week.
All participants who show up in the 4th floor hack room at DockerCon will get this way-cool magnet just for stopping by.

Quick links

Official hackathon page on Docs site
Event page on DockerCon website
View hackathon bugs on GitHub
Report your hackathon work
Browse prizes
docs on Slack, if you have questions

How it works
We have a number of bugs that have built up in our docs queue on GitHub, and we have labeled a whole slew of them with the tag hackathon, which you can see here.
Submit fixes for these bugs, or close them if you do a bit of research it turns out they aren’t actually valid. Every action you take gets you more points, and the points are redeemable for dollars in our hackathon store. These points also qualify you for valuable prizes like an Amazon gift card and a personally engraved trophy!
Prizes

All participants: Points are redeemable for t-shirts, hoodies, sweatshirts, mugs, beer steins, pint glasses, flasks, hoodies, stickers, buttons, magnets, wall clocks, post-cards, and even doggie t-shirts.
3rd place: A small trophy with a personal engraving, plus store credit
2nd place: A small trophy with a personal engraving, plus store credit, plus a $150 Amazon Gift Card
1st place: A large trophy with a personal engraving, plus store credit, plus a $300 Amazon Gift Card

Bonuses
A select few will get bonuses for being extra special contributors:

Largest single change introduced in a fix (files changed/lines of delta): 1000 points
Most bugs closed (resolved as no-op or handled): 1000 points
Most participation (attended all days): 1000 points

Choosing a prize
You can see the point values for the bugs in the GitHub queue. Those are worth cash in our rewards store at http://www.cafepress.com/dockerdocshackathon.
Our points-to-cash conversion rate will be figured out at the end of the hackathon, and will essentially be a function of the number of points that hackathon participants logged, and the number of dollars we have to spend on prizes.

View available rewards

When?
The docs hackathon is going on from April 17th thru April 21st, 2017. This is the time when it’s possible to claim and resolve bugs.
Where?
In-person
Attending DockerCon? Come to the fourth floor hack room on Tuesday and Wednesday from 1pm to 6pm. We’ll be there to answer questions and help you.
Note: While the hackathon is officially ongoing all week online, working in the hack room with us for these two days is by far the best way to participate; the docs team will be on-hand to get you started, get you unstuck, and guide you.
Online
Drop into the community Slack channel for the docs and ask any questions you have. Otherwise, just go to GitHub and look at our hackathon label and come here to claim your points when you’re done.
Claiming a bug
Whether attending in-person or online, to claim a bug as one that you are working on (so nobody else grabs it out from under you) you must type a comment saying you claim it. Respect it when you see other comments claiming a bug.

View available bugs

Claiming your points
Simply fill out this form when you’re done participating. We’ll take it from there.
Conversion rate
The points-to-cash ratio will be posted on the official page for the hackathon no later than Friday the 21st. We need to figure out how many points’ worth of fixes come in first.
Sorry but we can not send you cash for these points under any circumstances, even if you don’t spend them.
Questions?
Ask us anything at docs@docker.com or in the docs channel on Slack.
Thank you for participating in the 2017 Docs Hackathon!

Join us for the Docker Docs Hackathon: April 17-21, 2017Click To Tweet

The post Docker Docs Hackathon: April 17-21, 2017 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/