User Tools

Site Tools


cloud:naq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
cloud:naq [2020/05/14 09:25] – created chudlercloud:naq [2020/05/14 16:39] (current) chudler
Line 1: Line 1:
 === NAQ  (Never Asked Questions) === === NAQ  (Never Asked Questions) ===
  
-Q: Why does it use a self-signed certificate? 
-A: This is a loose end that might be addressed in the future. Let us know if it overburdens you. Note: we are unlikely to acknowledge security concerns associated with this. 
  
 Q: What are all of the services enabled? Q: What are all of the services enabled?
-A: +  * cinder
   * cinder-backup   * cinder-backup
 +  * cyborg
   * heat   * heat
   * barbican   * barbican
Line 15: Line 14:
   * manila   * manila
   * ganesha   * ganesha
-  * ceph (that is, ceph as a service. Your instances can be ceph clients in a software-defined manor if you wish, directly accessing RBD+  * ceph (that is, ceph-as-a-service. Your instances can access OSD directly, if you need
-  * MDS/RADOS/"Kitchen Sink" (you can have a distributed POSIX via ceph, or an object store, etc). +  * MDS/CephFS 
-  * swift +  * Swift Object Store 
-  * designate+  * Designate
   * DVR/HA   * DVR/HA
-  * Full Blown OVN, as you desire+  * Full Blown OVN, as you desire (No OpenDaylight is available)
   * nova   * nova
   * placement (standalone)   * placement (standalone)
 +  * Skydive (request for access)
   * glance   * glance
-  * gnocchi (as-a-service. Hundreds of metrics are collected for everything in your project)+  * gnocchi 
 +  * zun 
 +  * senlin 
 +  * ceilometer 
 + 
 +Q: What are the cloud services that are provided by those named above? 
 + 
 +A: Roughly speaking: 
 + 
 +  * Block Storage (e.g. EBS) 
 +  * Block Backup Service 
 +  * Hardware Acceleration (e.g. GPU) 
 +  * Declarative Cloud Automation (e.g. cloudformation) 
 +  * Secrets Storage Manager 
 +  * Workflow Service 
 +  * Hardware-as-a-service (non-virtualized) 
 +  * Load Balancing (nginx/haproxy-as-a-service) 
 +  * Data Processing (Hadoop/Spark/Storm) Service 
 +  * Software-defined NFS Service 
 +  * Object Storage (S3-compatible) 
 +  * Name Service (DNS) 
 +  * Virtual Routing and Virtual Networking 
 +  * General Compute virtualization (x86_64 focused) 
 +  * Real-time Network Analysis (restricted access) 
 +  * Image Storage Service 
 +  * Metrics Collection Service 
 +  * Container Runtime Service (**recommended**) 
 +  * Cluster Management Service 
 +  * Metering and Monitoring Service
  
 Q: What about containers (docker)? Q: What about containers (docker)?
 +
 A: [[ cloud:recipe:docker | Container Docs ]] A: [[ cloud:recipe:docker | Container Docs ]]
  
-Q: My servers are in ERROR state!!! +Q: I don't understand how to get started using it. 
-A: If the servers had been running previously, this is bad and may not be recoverable. Talk to us ASAP about anything that you know. We'll troubleshoot. The upside is that the servers might be gone but the volumes and anything else associated with them (ports, etc) can be attached to entirely new servers, as is often done in clouds.+ 
 +A: See "Getting and Using Access" in the [[ cloud:intro | Introduction ]].  
 + 
 +Q: Access methods? 
 + 
 +A:  
 +  * [[ cloud:cli | CLI ]]  
 +  * [[ https://overcloud.cs.uchicago.edu | Web ]] 
 +  * [[ cloud:recipe:coding | SDK ]]. 
 + 
 +Q: My servers are in ERROR state 
 + 
 +A: If the servers had been running previously, this is bad and may not be recoverable (!!). Talk to us ASAP about anything that you know. We'll troubleshoot. The upside is that the servers might be gone but the volumes and anything else associated with them (ports, etc) can be attached to entirely new servers, as is often done in clouds. 
 + 
 +Update: Ask about our newly supported [[ https://docs.openstack.org/nova/latest/user/rescue.html | Rescue Mode ]]
  
 Q: How fast is it? Q: How fast is it?
-A: We haven't done enough measurements, but believe it to be good enough for instructional use (compare with research use). There is some evidence that it can sustain 100MB/s random writes through to the backend+ 
 +A: We believe it to be good enough for instructional use (compare with research/HPC use). There is some evidence that it can sustain 100MB/s random writes through to the backend. Aside from I/O, we tolerate less than 50% over-commit of CPU.
  
 Q: Is my data safe? Q: Is my data safe?
-A: PROBABLY NOT AT THIS STAGE!  The backend is fully redundant and replicated 4x across a cluster of several dozen servers (etc, etc). The problem is that software failures are still happening on the backend and operators want to know why.+ 
 +A: The system is stable under known/ordinary/default setups. Virtual machine data is fully redundant and replicated 3x across a cluster.
  
 Q: How does the SSH key injection work? Q: How does the SSH key injection work?
 +
 A: Cloud-init. You won't be able to do this unless you are using a "cloud-ready" operating system A: Cloud-init. You won't be able to do this unless you are using a "cloud-ready" operating system
  
 Q: What operating systems are supported? Q: What operating systems are supported?
-A: We are prepared to run any workload if you are willing to put in requisite work also. We know it to be compatible with all major Unixes and Windows. Building an image is required before an instance can be launched and this is usually done with image building tools (chroot, et al).+ 
 +A: We are prepared to run any workload if you are willing to put in requisite work also. We know it to be compatible with all major Unixes and Windows. Building an image is required before an instance can be launched and this is usually done with image building tools. See [[ https://docs.openstack.org/image-guide/create-images-automatically.html | Image Tools ]].
  
 Q: What about limitations? Q: What about limitations?
 +
 A: The following quotas are set on your account and projects, only for the safety of the cloud. We will lift these easily if you need it (values are unspecified here, as yet, sorry): A: The following quotas are set on your account and projects, only for the safety of the cloud. We will lift these easily if you need it (values are unspecified here, as yet, sorry):
   * gigabytes   * gigabytes
Line 68: Line 116:
   * routers   * routers
  
 +Q: What do I need to bring to use this software?
 +
 +A: The following are requirements for consuming Compute Resources:
 +  * CNetID Authentication and affiliation to the Computer Science Department
 +  * Possession of SSH Key and knowledge of how to use it
 +
 +Everything else depends on what you will do with the resources that are available. [[ cloud:intro | The introduction ]] will guide you through managing your own cloud resources.
/var/lib/dokuwiki/data/attic/cloud/naq.1589466341.txt.gz · Last modified: 2020/05/14 09:25 by chudler

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki