Рейтинг
0.00

DigitalOcean Хостинг

9 читателей, 79 топиков

Introducing Our New Canadian Datacenter: TOR1



Today, we’re excited to announce the launch of our first Canadian datacenter in beautiful Toronto!

It's hard to deny that the Canadian startup ecosystem has been booming. There are nearly half a million software developers throughout Canada, and we at DigitalOcean have always felt lots of love from the Canadian developer community. Today we're excited to send some love back their way as we proudly open the doors to our Canadian datacenter, TOR1. Universe, a platform for people to discover and create events based in Toronto, is already a DigitalOcean customer. We are excited to help them expand their business in Canada.

This was a highly requested location. Each hypervisor comes equipped with 40GbE networking and the latest model of SSDs.

Because all of these Droplets will be physically in Canada, if your business needs to keep data in the Great White North, you’ll now be able to do that. DigitalOcean is committed to upholding the highest standards in privacy and security, and TOR1 enables us to extend those protections to our customers’ customers.

To celebrate the TOR1 launch with our friends in Canada, we'll be hosting events throughout October. Save the dates for your cities: Toronto (Oct 13-15), Vancouver (Oct 20-22), and Montreal (Oct 28 — 29). The official event details will be added to this post soon.

Head over to the Droplet create page or use the API to spin up a maple-flavored Droplet in TOR1 today!

Series B Funding

Объявили о закрытии очередного раунда финансирования. 



www.digitalocean.com/company/blog/series-b-funding-writing-a-new-chapter-in-the-digitalocean-story/
For over three years, we’ve been driven by the desire to empower developers and make cloud infrastructure simple. To date, over 500,000 developers have deployed more than 6 million Droplets on DigitalOcean and as the infrastructure needs of our developer community have continued to evolve, we have aspired to as well.
Today, we’re excited to announce that we’ve closed a Series B funding round worth $83 million, led by Access Industries with participation from Andreessen Horowitz. This funding represents our continued commitment to helping developers thrive and to help scaling startups grow on our infrastructure.
 

Introducing Team Accounts



Team Accounts Are Here!

This feature allows multiple users to access and manage an account's resources without having to share login or billing information.
A team account can be created by inviting new members to an existing DigitalOcean account. Working with team accounts is simple, however we do recommend reading our tutorial on the topic before you begin.
www.digitalocean.com/community/tutorials/how-to-use-digitalocean-team-accounts

Team accounts are also a great option for dev shops who would prefer to have their clients handle the billing. We’ve created a very simple guide covering team account creation that can be shared directly with clients to help them get set up.
www.digitalocean.com/community/tutorials/how-to-invite-your-web-developer-to-set-up-your-digitalocean-server

We’re excited about the opportunity to better support teams working collaboratively on DigitalOcean. For more details on this release, see our blog post.

Sunsetting DigitalOcean’s API v1

Since releasing version 2 of our API nearly a year ago and officially bringing it out of beta last month, we’ve seen a tremendous uptake of usage by our community. As the ecosystem of tools and libraries continues to grow, we’ve decided that it is time to sunset version 1 of the API.

Don’t worry! We’re not going to pull the rug out from under you. In order to give everyone time to port their tools, version 1 will not be turned off until November 1st 2015

With its (more) RESTful interface and features like OAuth support, v2 is both powerful and easy to use. Our developer documentation should give you all the information you need to begin the transition. If you have questions, you can always ask on our Community site or on Twitter.

DigitalOcean open Frankfurt location



We’re opening the new German region for business! Our new FRA1 facility, located in Frankfurt am Main, Germany, gives us an unparalleled opportunity to serve the growing German startup community and developers around the world.

We announced the new German region five months ago and after a month of build out, we are excited to open FRA1, operated by Interxion. The new region features our latest cloud spec and the full range of DigitalOcean features including Metadata, CoreOS, and IPv6.

New in FRA1:
  • 40 GbE network interfaces
  • Enhanced storage on hypervisors using our fastest-yet SSDs
We expect these features to provide the fast-growing German technology and information industry with DigitalOcean’s fastest-ever connectivity and hardware.

Due to its placement on the German Commercial Internet Exchange (DE-CIX), the largest Internet exchange point worldwide by peak traffic, this region also serves Germany’s neighboring countries with unparalleled connectivity and speeds. Like our other European locations, the German region meets Safe Harbor regulations for storing data.

The story of the German startup community is tremendous. We hope that by launching this new region, we can play our part in supporting innovation in Germany. You can try a server in FRA1 from the Droplet create page.

API v2 is now out of beta



We are very pleased to announce that API v2 is coming out of beta, nine months after its initial release. With this release we wanted to introduce new features not available in v1, while maintaining the level of simplicity developers loved in our first version. To help us keep it simple and stomp out bugs, we called on the community to collaborate with us in a public GitHub repository. The last nine months of collaboration with the community ensured our API remained awesome as we added these new features.

Our previous API was simple and easy to use. However, it lacked features allowing developers to interact with DigitalOcean in more advanced ways. We knew we wanted to include new features like:
  • OAuth
  • Pagination
  • A (more) RESTful interface
We wanted to add all of these features in v2, but were wary of increasing the complexity for our community. So, our first tactic was to introduce only new features the community was actually requesting. This involved taking internal and customer feedback even before launching in beta through UserVoice, internal dogfooding, and support tickets. Then during the beta, we received a constant stream of new feedback via the public GitHub repo.

Close collaboration with the community allowed us to fix several bugs as well as add a couple of very useful features. We received a high amount of feedback about the images endpoint, for example — specifically around filtering and maintaining an acceptable level of response time. Many of our users have a large number of snapshots and backups, so the ability to request different types of images via this endpoint proved very useful. Some other features which made it in thanks to community feedback include:
  • Increasing the base rate limit
  • Adding more information to the user endpoint
  • Clarifying the API documentation
  • Adding stronger validations to the Droplet creation process

Our second tactic was to keep the API as consistent as possible to reduce the cognitive load on the developer. As an example, we made sure all region objects in JSON responses follow the same format.

The final tactic was to beef up our API docs by launching our new developer portal. The new portal provides clear documentation, links to community tutorials to get started, and a centralized repository of API libraries.
We would like to thank everyone who helped report bugs and suggest features during the beta period. Thanks to you, API v2 is finally launched! Try it out here.

Easily Automate The Provisioning Of Your DigitalOcean Droplets!



www.digitalocean.com/company/blog/easily-automate-the-provisioning-of-your-droplets/

What kind of information is available via metadata?
Examples of available Droplet metadata include Droplet ID, data center region, IP addresses, and user-data.

What is user-data?
User-data is a special piece of metadata that can be provided by the user during the Droplet creation process. This data can be consumed by CloudInit to configure a server.

Which regions support metadata?
At launch, the SGP1, SFO1, LON1, AMS2, AMS3, & NYC3 regions have metadata available.

What is CloudInit?
CloudInit is a process enabled on recent DigitalOcean images that is able to pull down and process information from metadata. When the Droplet boots for the first time, the CloudInit program executes the script it finds in the “user-data” field, providing users the opportunity to automate the initial configuration of their servers.

Which images can process metadata information with CloudInit?
Currently, Ubuntu 14.04 and CentOS 7 base images have CloudInit enabled. Any one-click apps based on these releases will also have this functionality available. CoreOS servers also process the “user-data” field using a different mechanism.

Where can I learn more about using metadata and CloudInit?
We have prepared community articles that cover using the metadata service and writing scripts for CloudConfig. Also, our developer portal contains full documentation of the Metadata API.