true

1. Rob Hirschfeld, Dell
Twitter: @zehicle

2. “Multiple realities clouds of the quantum fog
condense into various chains of events, each chain
approximately observing the cause-and-effect
rules of classical physics. “
Gell-Mann/Hartle
EzineArticles.com/5970103
Extending the Fog.io cloud API abstraction
library to cover the OpenStack Quantum API.

3. A small ruby crystal [or gem],
mounted inside the resonant
cavity, provided a comparison
signal to help calibrate the
amplitude of the sample signal.
The sample and the ruby are
expected to vary in the same way
as the temperature fluctuates or
the spectrometer sensitivity drifts.
http://www.nobelprize.org/nobel_organizations/nobelfoundation/symposi
a/physics/ncs-2001-1/lee.pdf

4. Session Objective:
• Discuss integration of Quantum into Fog
Agenda:
• Objective
• CRUD Design
• Cloud Mapping
• Challenges
• Action items
http://spaceplace.nasa.gov/aerogel/

5. We want to encourage migration to Quantum
Targeting deployable bits (Folsom not Grizzly)
Barriers to adoption
1. Tooling build into workflow
2. Old network still works
3. Cross-cloud Compatibility
4. Others…?
http://stardust.jpl.nasa.gov/photo/aerogel.html

6.  Frodenas pushed to Fog Github late September
 Create/List Networks
 Create/List Ports
 Create/Lust Subnets
 Attach to Servers
 Good starting point!
 CRUD is not enough
Ferran Rodenas
Githib ID: frodenas

7.  VMware vSphere
 Amazon ECS networking
http://www.vinetechequipment.com/CroplandsVineyard.htm

8.  Automatically Create Networks by Default?
 Allow Switching between Nova & Quantum?
 Detect and use Quantum if available?
http://stardust.jpl.nasa.gov/images/gallery/aerogel_tracks.jpg

9.  Use Cases?
 Applications
 Mgmt Consoles
 Chef & Puppet
http://phys.org/news110556418.html
 Match Horizon Actions?
 Actions Transparent or Opaque?
 Generalized or OpenStack specific?

10.  Fog Development Tasks?
 Other API Abstraction Layers?
 Discussions
http://www.disinfo.com/2012/05/mouth-spray-makes-you-instantly-drunk/