Differences between revisions 50 and 52 (spanning 2 versions)
Revision 50 as of 2016-11-30 15:13:54
Size: 4958
Comment:
Revision 52 as of 2019-10-16 14:03:57
Size: 1869
Editor: ?ThomasLange
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
= Debian Cloud Sprint = = Debian Cloud Sprint 2016 =
Line 8: Line 8:

We have booked space for us all to meet in the Google Seattle office. The rooms we have are also equipped with wifi, AV equipment, and can support live Hangouts sessions for anyone to attend remotely. There is also ample space outside the rooms to split off into separate discussions or take breaks.

Address:
601 N. 34th Street
Seattle, WA 98103
https://goo.gl/maps/EzKKmrFu2Ju

Mass Transit options:
Several bus routes from downtown Seattle, the University of Washington, and around town go directly to the Google office in Fremont. Routes 31, 32, 40, and 62 stop across the street. Routes 5, 26, 28, and 82 are within walking distance up the hill.
http://metro.kingcounty.gov/ Routes 31 and 32 are the most convenient from the University Inn hotel, where many attendees are staying. See [[https://lists.debian.org/debian-cloud/2016/10/msg00028.html|zobe's post 1]] and [[https://lists.debian.org/debian-cloud/2016/10/msg00030.html|zobel's post 2]] for some details.

If you are going to be using public transit- including the Light Rail from the airport, look into getting an Orca card when you arrive to make your life easier.
http://kingcounty.gov/depts/transportation/metro/fares-orca.aspx

Parking options:
Street parking and pay to park lots are available nearby. The nearby U-Park lots are Lot 52, Lot 58, Lot 62, Lot 71, Lot 72, Fremont #81, and the Red Door Lower Garage #71B.
http://www.u-parksystem.com/locations/default.asp#fremont_seattle

Coffee, water, light snacks in the morning, as well as lunch will be on site provided by Google.

== Other Logistics ==

Staying in or around downtown Seattle is usually easiest in terms of getting around. The Link Light Rail goes directly from the airport to many places downtown and also onto the University. Bus, Lyft, or Uber to the Google Fremont office is fairly trivial from anywhere downtown. Feel free to reach out if you require any other information here.

Lee Fisher offered the use of Black Lodge Research, a community hacker lodge as a fallback option for the event. There is an open hacker night on Thursday at the lodge if anyone is interested in doing something completely different one night. The lodge is located in Redmond, WA (on the east side of Lake Washington from Seattle). So if you are interested in checking out this event, plan ahead for transportation to get from Seattle to Redmond. http://www.blacklodgeresearch.org/
Line 62: Line 36:
== Google Hangouts ==
The following Google Hangouts session can be used to interact with the Seattle meeting space throughout the entirety of the sprint. This hangout will be active from about 9AM Pacific to about 6PM Pacific (ish) on the days in question.
https://hangouts.google.com/hangouts/_/google.com/debian-cloud-2

If you want to present your screen to the room, use this URL:
https://hangouts.google.com/hangouts/_/present/google.com/debian-cloud-2
Line 95: Line 62:
== Acknowledgements ==

the sprint has been possible thanks to:

 * [[http://www.debian.org/donations|donations]] to the Debian project
 * [[http://www.google.com/|Google]] for hosting us

Debian Cloud Sprint 2016

Location, Date

  • when: November 2-4, 2016
  • where: Google, Seattle, WA USA

Participants

Please note if you are attending remotely via Hangouts. We will have a live Hangouts session running the whole time.

Agenda

Debian In The Cloud

  • What does it mean to run in a cloud environment.
  • In depth look at how Debian runs in major clouds (AWS, Azure, GCE... etc)
  • Look into different build processes of different image types (maybe short presentations)
  • Define an official Debian cloud image.
  • Introspect the various image build tools and whittle the list down.
  • Versioning 'Cloud Images' and critical hols patching policy (example: dirty CoW, heartblead, etc)
  • Ideally, come to consensus on many of the open ended issues that have been talked about at DebConf and on the debian-cloud list.

(tentative/final agenda here before/after the sprint)

Reports

(pointers to communication about the sprint)

Group Photo

group_photo.jpg


CategorySprint