misty 0.9.0 → 0.9.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +37 -35
- data/lib/misty/cloud.rb +0 -2
- data/lib/misty/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: cf1c5c6f54a2f26de7e2a55a2d5f4bd169e68431
|
4
|
+
data.tar.gz: 1e471a166e49dd7c4d10441593a39976f2662c8f
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: bbbd202a09f147d4cd8e5a100efc2028b32e76cac9bacd44cc6d0a5a8979b940d2f69000f808e8c4c868d860ef771731b39002f759a167e79c11658fc0f400c6
|
7
|
+
data.tar.gz: 03aab150f96558bf2a3428a4c31447248cade4790f2462ee1edc28e0b65a12f4dfbc49041b8ce1c992927648b916df50b7dc0782e2b219a2ce80dcf6bbad4bd6
|
data/README.md
CHANGED
@@ -81,44 +81,46 @@ openstack.network.create_network('network': {'name': 'my-network'})
|
|
81
81
|
|
82
82
|
To obtain the list of supported services:
|
83
83
|
```ruby
|
84
|
-
require 'misty'
|
85
|
-
puts Misty.services
|
84
|
+
> require 'misty'
|
85
|
+
> puts Misty.services
|
86
|
+
application_catalog: murano, versions: ["v1"]
|
87
|
+
alarming: aodh, versions: ["v2"]
|
88
|
+
backup: freezer, versions: ["v1"]
|
89
|
+
baremetal: ironic, microversion: v1
|
90
|
+
block_storage: cinder, versions: ["v2", "v1"], microversion: v3
|
91
|
+
clustering: senlin, versions: ["v1"]
|
92
|
+
compute: nova, microversion: v2.1
|
93
|
+
container_infrastructure_management: magnum, microversion: v1
|
94
|
+
data_processing: sahara, versions: ["v1.1"]
|
95
|
+
data_protection_orchestration: karbor, versions: ["v1"]
|
96
|
+
database: trove, versions: ["v1.0"]
|
97
|
+
domain_name_server: designate, versions: ["v2"]
|
98
|
+
identity: keystone, versions: ["v3", "v2.0"]
|
99
|
+
image: glance, versions: ["v2", "v1"]
|
100
|
+
load_balancer: octavia, versions: ["v2.0"]
|
101
|
+
messaging: zaqar, versions: ["v2"]
|
102
|
+
metering: ceilometer, versions: ["v2"]
|
103
|
+
networking: neutron, versions: ["v2.0"]
|
104
|
+
nfv_orchestration: tacker, versions: ["v1.0"]
|
105
|
+
object_storage: swift, versions: ["v1"]
|
106
|
+
orchestration: heat, versions: ["v1"]
|
107
|
+
search: searchlight, versions: ["v1"]
|
108
|
+
shared_file_systems: manila, microversion: v2
|
86
109
|
```
|
87
110
|
|
88
|
-
|
89
|
-
|
90
|
-
|
91
|
-
|
92
|
-
|
93
|
-
|
94
|
-
|
95
|
-
|
96
|
-
|
97
|
-
|
98
|
-
|
99
|
-
container | magnum | ["v1"]
|
100
|
-
data_processing | sahara | ["v1.1"]
|
101
|
-
data_protection | karbor | ["v1"]
|
102
|
-
database | trove | ["v1.0"]
|
103
|
-
dns | designate | ["v2"]
|
104
|
-
identity | keystone | ["v3", "v2.0"]
|
105
|
-
image | glance | ["v2", "v1"]
|
106
|
-
load_balancer | octavia | ["v2.0"]
|
107
|
-
messaging | zaqar | ["v2"]
|
108
|
-
metering | ceilometer | ["v2"]
|
109
|
-
networking | neutron | ["v2.0"]
|
110
|
-
nfv_orchestration | tacker | ["v1.0"]
|
111
|
-
object_storage | swift | ["v1"]
|
112
|
-
orchestration | heat | ["v1"]
|
113
|
-
search | searchlight | ["v1"]
|
114
|
-
shared_file_systems | manila | ["v2"]
|
115
|
-
|
116
|
-
* Notes
|
117
|
-
When an Openstack service requires a different service name, the :service_names option can be used (see below).
|
118
|
-
`volume` is an alias for `block_storage`.
|
119
|
-
Unique prefixed service names can be used: For instance `network` (or even `net`) instead of `networking`. Meanwhile
|
120
|
-
`data` doesn't work because it's ambiguous between `data_processing` and `data_protection`
|
111
|
+
### Prefixes
|
112
|
+
A shorter name can be used to call a service only if it's unique among all services.
|
113
|
+
For instance `net` or `network` can be used instead of `networking`.
|
114
|
+
Meanwhile `data` doesn't work because it's ambiguous between `data_processing` and `data_protection_orchestration`
|
115
|
+
|
116
|
+
### Aliases
|
117
|
+
* `dns` is an alias for `domain_name_server`
|
118
|
+
* `volume` is an alias for `block_storage`
|
119
|
+
|
120
|
+
## Openstack service name
|
121
|
+
Different service names can be used for a specific Openstack Service by using the :service_names option (see below).
|
121
122
|
|
123
|
+
## Requests
|
122
124
|
The #requests method provides the available requests for a service, for example:
|
123
125
|
```ruby
|
124
126
|
openstack.compute.requests
|
data/lib/misty/cloud.rb
CHANGED
@@ -131,8 +131,6 @@ module Misty
|
|
131
131
|
@shared_file_systems ||= build_service(:shared_file_systems)
|
132
132
|
end
|
133
133
|
|
134
|
-
alias container container_infrastructure_management
|
135
|
-
alias data_protection data_protection_orchestration
|
136
134
|
alias dns domain_name_server
|
137
135
|
alias volume block_storage
|
138
136
|
|
data/lib/misty/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: misty
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.9.
|
4
|
+
version: 0.9.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Gilles Dubreuil
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2017-09-
|
11
|
+
date: 2017-09-08 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: json
|