flight_facade 0.1.1

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: 9f552d4d94742a652729938a6131e6da6af31016c09c1957d353e6347b83b10b
4
+ data.tar.gz: 8dc5ae689f5314f5cd582fb9217df6775f1f3ec22b69d778737f21ce8680e74d
5
+ SHA512:
6
+ metadata.gz: 3d2bd5a1490e489445a6bf00dda53b68d1292c0cc06f292995550a2c77fbe69813d1eff24d613bba7275a2b7ffd1497772983b81da7c4de86dabc2d5f08b566e
7
+ data.tar.gz: b8b2f87a74fb5573bdacfc9b2d59e56eb7f3ba5dd6b601108f52f1d455f0cac05a59538ebd65f8a4c376d2d6b812962d9813e0cdfd30ee2f315e96af6a408a63
@@ -0,0 +1,12 @@
1
+ /.bundle/
2
+ /.yardoc
3
+ /_yardoc/
4
+ /coverage/
5
+ /doc/
6
+ /pkg/
7
+ /spec/reports/
8
+ /tmp/
9
+ Gemfile.lock
10
+
11
+ # rspec failure tracking
12
+ .rspec_status
data/.rspec ADDED
@@ -0,0 +1,3 @@
1
+ --format documentation
2
+ --color
3
+ --require spec_helper
@@ -0,0 +1,8 @@
1
+ ---
2
+ sudo: false
3
+ language: ruby
4
+ cache: bundler
5
+ rvm:
6
+ - 2.5.3
7
+ - 2.6.5
8
+ before_install: gem install bundler -v 2.0.2
@@ -0,0 +1,74 @@
1
+ # Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ nationality, personal appearance, race, religion, or sexual identity and
10
+ orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behaviour that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behaviour by participants include:
24
+
25
+ * The use of sexualised language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behaviour and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behaviour.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviours that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behaviour may be
58
+ reported by contacting the project team at [help@openflighthpc.org](help@openflighthpc.org). All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at [http://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: http://contributor-covenant.org
74
+ [version]: http://contributor-covenant.org/version/1/4/
@@ -0,0 +1,184 @@
1
+ # Contributing to Power Server
2
+
3
+ :+1::tada: Thanks for taking the time to contribute! :tada::+1:
4
+
5
+ You want to contribute to Power Server? Welcome! Please read this
6
+ document to understand what you can do:
7
+
8
+ * [Code of Conduct](#code-of-conduct)
9
+ * [Help Others](#help-others)
10
+ * [Analyse Issues](#analyse-issues)
11
+ * [Report an Issue](#report-an-issue)
12
+ * [Contribute Changes](#contribute-changes)
13
+
14
+ When contributing to this repository, please first discuss the change
15
+ you wish to make via a Github issue or a post on the [OpenFlight
16
+ Community site](https://community.openflighthpc.org).
17
+
18
+ Please note we have a [code of conduct](CODE_OF_CONDUCT.md), please
19
+ follow it in all your interactions with the project.
20
+
21
+ ## Code of Conduct
22
+
23
+ This project and everyone participating in it is governed by the
24
+ [OpenFlight Code of Conduct](CODE_OF_CONDUCT.md). By participating,
25
+ you are expected to uphold this code. Please report unacceptable
26
+ behaviour to [help@openflighthpc.org](mailto:help@openflighthpc.org).
27
+
28
+ ## Help Others
29
+
30
+ You can help Power Server by helping others who use it and need support.
31
+
32
+ ## Analyse Issues
33
+
34
+ Analysing issue reports can be a lot of effort. Any help is welcome!
35
+ Go to [the GitHub issue tracker](https://github.com/openflighthpc/power-server/issues?state=open)
36
+ and find an open issue which needs additional work or a bugfix
37
+ (e.g. issues labeled with "help wanted" or "bug").
38
+
39
+ Additional work could include any further information, or a gist, or
40
+ it might be a hint that helps understanding the issue. Maybe you can
41
+ even find and [contribute](#contribute-changes) a bugfix?
42
+
43
+ ## Report an Issue
44
+
45
+ If you find a bug - behaviour of Power Server code or documentation
46
+ contradicting your expectation - you are welcome to report it. We can
47
+ only handle well-reported, actual bugs, so please follow the
48
+ guidelines below.
49
+
50
+ Once you have familiarised with the guidelines, you can go to the
51
+ [GitHub issue tracker for Power Server](https://github.com/openflighthpc/power-server/issues/new)
52
+ to report the issue.
53
+
54
+ ### Quick Checklist for Bug Reports
55
+
56
+ Issue report checklist:
57
+
58
+ * Real, current bug
59
+ * No duplicate
60
+ * Reproducible
61
+ * Good summary
62
+ * Well-documented
63
+ * Minimal example
64
+
65
+ ### Issue handling process
66
+
67
+ When an issue is reported, a committer will look at it and either
68
+ confirm it as a real issue, close it if it is not an issue, or ask for
69
+ more details.
70
+
71
+ An issue that is about a real bug is closed as soon as the fix is committed.
72
+
73
+ ### Reporting Security Issues
74
+
75
+ If you find a security issue, please act responsibly and report it not
76
+ in the public issue tracker, but directly to us, so we can fix it
77
+ before it can be exploited. Please send the related information to
78
+ [security@openflighthpc.org](mailto:security@openflighthpc.org).
79
+
80
+ ### Issue Reporting Disclaimer
81
+
82
+ We want to improve the quality of Power Server and good bug reports are
83
+ welcome! However, our capacity is limited, thus we reserve the right
84
+ to close or to not process bug reports with insufficient detail in
85
+ favour of those which are very cleanly documented and easy to
86
+ reproduce. Even though we would like to solve each well-documented
87
+ issue, there is always the chance that it will not happen - remember:
88
+ Power Server is Open Source and comes without warranty.
89
+
90
+ Bug report analysis support is very welcome! (e.g. pre-analysis or
91
+ proposing solutions)
92
+
93
+ ## Contribute Changes
94
+
95
+ You are welcome to contribute code, content or documentation to
96
+ Power Server in order to fix bugs or to implement new features.
97
+
98
+ There are three important things to know:
99
+
100
+ 1. You must be aware of the Eclipse Public License 2.0 (which
101
+ describes contributions) and **agree to the Contributors License
102
+ Agreement**. This is common practice in all major Open Source
103
+ projects.
104
+ 2. **Not all proposed contributions can be accepted**. Some features
105
+ may e.g. just fit a third-party add-on better. The change must fit
106
+ the overall direction of Power Server and really improve it. The more
107
+ effort you invest, the better you should clarify in advance whether
108
+ the contribution fits: the best way would be to just open an issue
109
+ to discuss the feature you plan to implement (make it clear you
110
+ intend to contribute).
111
+
112
+ ### Contributor License Agreement
113
+
114
+ When you contribute (code, documentation, or anything else), you have
115
+ to be aware that your contribution is covered by the same [Eclipse
116
+ Public License 2.0](https://opensource.org/licenses/EPL-2.0) that is
117
+ applied to Power Server itself.
118
+
119
+ In particular you need to agree to the Contributor License Agreement,
120
+ which can be [found
121
+ here](https://www.clahub.com/agreements/openflighthpc/power-server). This
122
+ applies to all contributors, including those contributing on behalf of
123
+ a company. If you agree to its content, you simply have to click on
124
+ the link posted by the CLA assistant available on the pull
125
+ request. Click it to check the CLA, then accept it on the following
126
+ screen if you agree to it. CLA assistant will save this decision for
127
+ upcoming contributions and will notify you if there is any change to
128
+ the CLA in the meantime.
129
+
130
+ ## Pull Request Process
131
+
132
+ 1. Make sure the change would be welcome (e.g. a bugfix or a useful
133
+ feature); best do so by proposing it in a GitHub issue.
134
+ 2. Fork, then clone the repo.
135
+ 3. Make your changes ([see below](#making-changes)) and commit.
136
+ 4. In the commit message:
137
+ - Describe the problem you fix with this change.
138
+ - Describe the effect that this change has from a user's point of
139
+ view. App crashes and lockups are pretty convincing for example,
140
+ but not all bugs are that obvious and should be mentioned in the
141
+ text.
142
+ - Describe the technical details of what you changed. It is
143
+ important to describe the change in a most understandable way so
144
+ the reviewer is able to verify that the code is behaving as you
145
+ intend it to.
146
+ 5. If your change fixes an issue reported at GitHub, add the following
147
+ line to the commit message:
148
+ - `Fixes #(issueNumber)`
149
+ - Do NOT add a colon after "Fixes" - this prevents automatic closing.
150
+ 6. Open a pull request!
151
+ 7. Follow the link posted by the CLA assistant to your pull request
152
+ and accept it, as described in detail above.
153
+ 8. Wait for our code review and approval, possibly enhancing your
154
+ change on request.
155
+ - Note that the Power Server developers also have their regular
156
+ duties, so depending on the required effort for reviewing,
157
+ testing and clarification this may take a while.
158
+ 9. Once the change has been approved we will inform you in a comment.
159
+ 10. We will close the pull request; feel free to delete the now
160
+ obsolete branch.
161
+
162
+ ## Making Changes
163
+
164
+ 1. Create a topic branch from where you want to base your work.
165
+ * This is usually the `master` branch.
166
+ * Only target release branches if you are certain your fix must be
167
+ on that branch.
168
+ * To quickly create a topic branch based on master, run `git
169
+ checkout -b fix/master/my_contribution master`. Please avoid
170
+ working directly on the `master` branch.
171
+ 2. Make commits of logical and atomic units.
172
+ 3. Check for unnecessary whitespace with `git diff --check` before
173
+ committing.
174
+
175
+ ## Attribution
176
+
177
+ These contribution guidelines are adapted from
178
+ [various](https://github.com/cla-assistant/cla-assistant/blob/master/CONTRIBUTING.md)
179
+ [previous](https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md)
180
+ [contribution](https://gist.github.com/PurpleBooth/b24679402957c63ec426)
181
+ [guideline](https://github.com/atom/atom/blob/master/CONTRIBUTING.md)
182
+ documents from other projects hosted on Github. Our thanks to the
183
+ respective authors for making contributing to Open Source projects a
184
+ more streamlined and efficient process!
data/Gemfile ADDED
@@ -0,0 +1,4 @@
1
+ source "https://rubygems.org"
2
+
3
+ # Specify your gem's dependencies in flight_facade.gemspec
4
+ gemspec
@@ -0,0 +1,277 @@
1
+ Eclipse Public License - v 2.0
2
+
3
+ THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE
4
+ PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
5
+ OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
6
+
7
+ 1. DEFINITIONS
8
+
9
+ "Contribution" means:
10
+
11
+ a) in the case of the initial Contributor, the initial content
12
+ Distributed under this Agreement, and
13
+
14
+ b) in the case of each subsequent Contributor:
15
+ i) changes to the Program, and
16
+ ii) additions to the Program;
17
+ where such changes and/or additions to the Program originate from
18
+ and are Distributed by that particular Contributor. A Contribution
19
+ "originates" from a Contributor if it was added to the Program by
20
+ such Contributor itself or anyone acting on such Contributor's behalf.
21
+ Contributions do not include changes or additions to the Program that
22
+ are not Modified Works.
23
+
24
+ "Contributor" means any person or entity that Distributes the Program.
25
+
26
+ "Licensed Patents" mean patent claims licensable by a Contributor which
27
+ are necessarily infringed by the use or sale of its Contribution alone
28
+ or when combined with the Program.
29
+
30
+ "Program" means the Contributions Distributed in accordance with this
31
+ Agreement.
32
+
33
+ "Recipient" means anyone who receives the Program under this Agreement
34
+ or any Secondary License (as applicable), including Contributors.
35
+
36
+ "Derivative Works" shall mean any work, whether in Source Code or other
37
+ form, that is based on (or derived from) the Program and for which the
38
+ editorial revisions, annotations, elaborations, or other modifications
39
+ represent, as a whole, an original work of authorship.
40
+
41
+ "Modified Works" shall mean any work in Source Code or other form that
42
+ results from an addition to, deletion from, or modification of the
43
+ contents of the Program, including, for purposes of clarity any new file
44
+ in Source Code form that contains any contents of the Program. Modified
45
+ Works shall not include works that contain only declarations,
46
+ interfaces, types, classes, structures, or files of the Program solely
47
+ in each case in order to link to, bind by name, or subclass the Program
48
+ or Modified Works thereof.
49
+
50
+ "Distribute" means the acts of a) distributing or b) making available
51
+ in any manner that enables the transfer of a copy.
52
+
53
+ "Source Code" means the form of a Program preferred for making
54
+ modifications, including but not limited to software source code,
55
+ documentation source, and configuration files.
56
+
57
+ "Secondary License" means either the GNU General Public License,
58
+ Version 2.0, or any later versions of that license, including any
59
+ exceptions or additional permissions as identified by the initial
60
+ Contributor.
61
+
62
+ 2. GRANT OF RIGHTS
63
+
64
+ a) Subject to the terms of this Agreement, each Contributor hereby
65
+ grants Recipient a non-exclusive, worldwide, royalty-free copyright
66
+ license to reproduce, prepare Derivative Works of, publicly display,
67
+ publicly perform, Distribute and sublicense the Contribution of such
68
+ Contributor, if any, and such Derivative Works.
69
+
70
+ b) Subject to the terms of this Agreement, each Contributor hereby
71
+ grants Recipient a non-exclusive, worldwide, royalty-free patent
72
+ license under Licensed Patents to make, use, sell, offer to sell,
73
+ import and otherwise transfer the Contribution of such Contributor,
74
+ if any, in Source Code or other form. This patent license shall
75
+ apply to the combination of the Contribution and the Program if, at
76
+ the time the Contribution is added by the Contributor, such addition
77
+ of the Contribution causes such combination to be covered by the
78
+ Licensed Patents. The patent license shall not apply to any other
79
+ combinations which include the Contribution. No hardware per se is
80
+ licensed hereunder.
81
+
82
+ c) Recipient understands that although each Contributor grants the
83
+ licenses to its Contributions set forth herein, no assurances are
84
+ provided by any Contributor that the Program does not infringe the
85
+ patent or other intellectual property rights of any other entity.
86
+ Each Contributor disclaims any liability to Recipient for claims
87
+ brought by any other entity based on infringement of intellectual
88
+ property rights or otherwise. As a condition to exercising the
89
+ rights and licenses granted hereunder, each Recipient hereby
90
+ assumes sole responsibility to secure any other intellectual
91
+ property rights needed, if any. For example, if a third party
92
+ patent license is required to allow Recipient to Distribute the
93
+ Program, it is Recipient's responsibility to acquire that license
94
+ before distributing the Program.
95
+
96
+ d) Each Contributor represents that to its knowledge it has
97
+ sufficient copyright rights in its Contribution, if any, to grant
98
+ the copyright license set forth in this Agreement.
99
+
100
+ e) Notwithstanding the terms of any Secondary License, no
101
+ Contributor makes additional grants to any Recipient (other than
102
+ those set forth in this Agreement) as a result of such Recipient's
103
+ receipt of the Program under the terms of a Secondary License
104
+ (if permitted under the terms of Section 3).
105
+
106
+ 3. REQUIREMENTS
107
+
108
+ 3.1 If a Contributor Distributes the Program in any form, then:
109
+
110
+ a) the Program must also be made available as Source Code, in
111
+ accordance with section 3.2, and the Contributor must accompany
112
+ the Program with a statement that the Source Code for the Program
113
+ is available under this Agreement, and informs Recipients how to
114
+ obtain it in a reasonable manner on or through a medium customarily
115
+ used for software exchange; and
116
+
117
+ b) the Contributor may Distribute the Program under a license
118
+ different than this Agreement, provided that such license:
119
+ i) effectively disclaims on behalf of all other Contributors all
120
+ warranties and conditions, express and implied, including
121
+ warranties or conditions of title and non-infringement, and
122
+ implied warranties or conditions of merchantability and fitness
123
+ for a particular purpose;
124
+
125
+ ii) effectively excludes on behalf of all other Contributors all
126
+ liability for damages, including direct, indirect, special,
127
+ incidental and consequential damages, such as lost profits;
128
+
129
+ iii) does not attempt to limit or alter the recipients' rights
130
+ in the Source Code under section 3.2; and
131
+
132
+ iv) requires any subsequent distribution of the Program by any
133
+ party to be under a license that satisfies the requirements
134
+ of this section 3.
135
+
136
+ 3.2 When the Program is Distributed as Source Code:
137
+
138
+ a) it must be made available under this Agreement, or if the
139
+ Program (i) is combined with other material in a separate file or
140
+ files made available under a Secondary License, and (ii) the initial
141
+ Contributor attached to the Source Code the notice described in
142
+ Exhibit A of this Agreement, then the Program may be made available
143
+ under the terms of such Secondary Licenses, and
144
+
145
+ b) a copy of this Agreement must be included with each copy of
146
+ the Program.
147
+
148
+ 3.3 Contributors may not remove or alter any copyright, patent,
149
+ trademark, attribution notices, disclaimers of warranty, or limitations
150
+ of liability ("notices") contained within the Program from any copy of
151
+ the Program which they Distribute, provided that Contributors may add
152
+ their own appropriate notices.
153
+
154
+ 4. COMMERCIAL DISTRIBUTION
155
+
156
+ Commercial distributors of software may accept certain responsibilities
157
+ with respect to end users, business partners and the like. While this
158
+ license is intended to facilitate the commercial use of the Program,
159
+ the Contributor who includes the Program in a commercial product
160
+ offering should do so in a manner which does not create potential
161
+ liability for other Contributors. Therefore, if a Contributor includes
162
+ the Program in a commercial product offering, such Contributor
163
+ ("Commercial Contributor") hereby agrees to defend and indemnify every
164
+ other Contributor ("Indemnified Contributor") against any losses,
165
+ damages and costs (collectively "Losses") arising from claims, lawsuits
166
+ and other legal actions brought by a third party against the Indemnified
167
+ Contributor to the extent caused by the acts or omissions of such
168
+ Commercial Contributor in connection with its distribution of the Program
169
+ in a commercial product offering. The obligations in this section do not
170
+ apply to any claims or Losses relating to any actual or alleged
171
+ intellectual property infringement. In order to qualify, an Indemnified
172
+ Contributor must: a) promptly notify the Commercial Contributor in
173
+ writing of such claim, and b) allow the Commercial Contributor to control,
174
+ and cooperate with the Commercial Contributor in, the defense and any
175
+ related settlement negotiations. The Indemnified Contributor may
176
+ participate in any such claim at its own expense.
177
+
178
+ For example, a Contributor might include the Program in a commercial
179
+ product offering, Product X. That Contributor is then a Commercial
180
+ Contributor. If that Commercial Contributor then makes performance
181
+ claims, or offers warranties related to Product X, those performance
182
+ claims and warranties are such Commercial Contributor's responsibility
183
+ alone. Under this section, the Commercial Contributor would have to
184
+ defend claims against the other Contributors related to those performance
185
+ claims and warranties, and if a court requires any other Contributor to
186
+ pay any damages as a result, the Commercial Contributor must pay
187
+ those damages.
188
+
189
+ 5. NO WARRANTY
190
+
191
+ EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENT
192
+ PERMITTED BY APPLICABLE LAW, THE PROGRAM IS PROVIDED ON AN "AS IS"
193
+ BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
194
+ IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF
195
+ TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
196
+ PURPOSE. Each Recipient is solely responsible for determining the
197
+ appropriateness of using and distributing the Program and assumes all
198
+ risks associated with its exercise of rights under this Agreement,
199
+ including but not limited to the risks and costs of program errors,
200
+ compliance with applicable laws, damage to or loss of data, programs
201
+ or equipment, and unavailability or interruption of operations.
202
+
203
+ 6. DISCLAIMER OF LIABILITY
204
+
205
+ EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENT
206
+ PERMITTED BY APPLICABLE LAW, NEITHER RECIPIENT NOR ANY CONTRIBUTORS
207
+ SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
208
+ EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
209
+ PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
210
+ CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
211
+ ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE
212
+ EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE
213
+ POSSIBILITY OF SUCH DAMAGES.
214
+
215
+ 7. GENERAL
216
+
217
+ If any provision of this Agreement is invalid or unenforceable under
218
+ applicable law, it shall not affect the validity or enforceability of
219
+ the remainder of the terms of this Agreement, and without further
220
+ action by the parties hereto, such provision shall be reformed to the
221
+ minimum extent necessary to make such provision valid and enforceable.
222
+
223
+ If Recipient institutes patent litigation against any entity
224
+ (including a cross-claim or counterclaim in a lawsuit) alleging that the
225
+ Program itself (excluding combinations of the Program with other software
226
+ or hardware) infringes such Recipient's patent(s), then such Recipient's
227
+ rights granted under Section 2(b) shall terminate as of the date such
228
+ litigation is filed.
229
+
230
+ All Recipient's rights under this Agreement shall terminate if it
231
+ fails to comply with any of the material terms or conditions of this
232
+ Agreement and does not cure such failure in a reasonable period of
233
+ time after becoming aware of such noncompliance. If all Recipient's
234
+ rights under this Agreement terminate, Recipient agrees to cease use
235
+ and distribution of the Program as soon as reasonably practicable.
236
+ However, Recipient's obligations under this Agreement and any licenses
237
+ granted by Recipient relating to the Program shall continue and survive.
238
+
239
+ Everyone is permitted to copy and distribute copies of this Agreement,
240
+ but in order to avoid inconsistency the Agreement is copyrighted and
241
+ may only be modified in the following manner. The Agreement Steward
242
+ reserves the right to publish new versions (including revisions) of
243
+ this Agreement from time to time. No one other than the Agreement
244
+ Steward has the right to modify this Agreement. The Eclipse Foundation
245
+ is the initial Agreement Steward. The Eclipse Foundation may assign the
246
+ responsibility to serve as the Agreement Steward to a suitable separate
247
+ entity. Each new version of the Agreement will be given a distinguishing
248
+ version number. The Program (including Contributions) may always be
249
+ Distributed subject to the version of the Agreement under which it was
250
+ received. In addition, after a new version of the Agreement is published,
251
+ Contributor may elect to Distribute the Program (including its
252
+ Contributions) under the new version.
253
+
254
+ Except as expressly stated in Sections 2(a) and 2(b) above, Recipient
255
+ receives no rights or licenses to the intellectual property of any
256
+ Contributor under this Agreement, whether expressly, by implication,
257
+ estoppel or otherwise. All rights in the Program not expressly granted
258
+ under this Agreement are reserved. Nothing in this Agreement is intended
259
+ to be enforceable by any entity that is not a Contributor or Recipient.
260
+ No third-party beneficiary rights are created under this Agreement.
261
+
262
+ Exhibit A - Form of Secondary Licenses Notice
263
+
264
+ "This Source Code may also be made available under the following
265
+ Secondary Licenses when the conditions for such availability set forth
266
+ in the Eclipse Public License, v. 2.0 are satisfied: {name license(s),
267
+ version(s), and exceptions or additional permissions here}."
268
+
269
+ Simply including a copy of this Agreement, including this Exhibit A
270
+ is not sufficient to license the Source Code under Secondary Licenses.
271
+
272
+ If it is not possible or desirable to put the notice in a particular
273
+ file, then You may include the notice in a location (such as a LICENSE
274
+ file in a relevant directory) where a recipient would be likely to
275
+ look for such a notice.
276
+
277
+ You may add additional accurate notices of copyright ownership.
@@ -0,0 +1,44 @@
1
+ # FlightFacade
2
+
3
+ Provides a standardised set of interfaces to cluster concepts. These interfaces can be either configured to work in a standalone mode OR integrate with other services.
4
+
5
+ ## Installation
6
+
7
+ Add this line to your application's Gemfile:
8
+
9
+ ```ruby
10
+ gem 'flight_facade'
11
+ ```
12
+
13
+ And then execute:
14
+
15
+ $ bundle
16
+
17
+ Or install it yourself as:
18
+
19
+ $ gem install flight_facade
20
+
21
+ ## Usage
22
+
23
+ TODO: Write usage instructions here
24
+
25
+ ## Development
26
+
27
+ After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
28
+
29
+ To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
30
+
31
+ ## Contributing
32
+
33
+ Fork the project. Make your feature addition or bug fix. Send a pull request. Bonus points for topic branches.
34
+
35
+ Read CONTRIBUTING.md for more details.
36
+
37
+ ## Copyright and License
38
+ Eclipse Public License 2.0, see LICENSE.txt for details.
39
+
40
+ Copyright (C) 2019-present Alces Flight Ltd.
41
+
42
+ This program and the accompanying materials are made available under the terms of the Eclipse Public License 2.0 which is available at https://www.eclipse.org/legal/epl-2.0, or alternative license terms made available by Alces Flight Ltd - please direct inquiries about licensing to licensing@alces-flight.com.
43
+
44
+ FlightFacade is distributed in the hope that it will be useful, but WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the Eclipse Public License 2.0 for more details.
@@ -0,0 +1,6 @@
1
+ require "bundler/gem_tasks"
2
+ require "rspec/core/rake_task"
3
+
4
+ RSpec::Core::RakeTask.new(:spec)
5
+
6
+ task :default => :spec
@@ -0,0 +1,11 @@
1
+ #!/usr/bin/env ruby
2
+
3
+ require "bundler/setup"
4
+ require "flight_facade"
5
+
6
+ # You can add fixtures and/or initialization code here to make experimenting
7
+ # with your gem easier. You can also use a different console, if you like.
8
+
9
+ # (If you use this, don't forget to add pry to your Gemfile!)
10
+ require "pry"
11
+ Pry.start
@@ -0,0 +1,8 @@
1
+ #!/usr/bin/env bash
2
+ set -euo pipefail
3
+ IFS=$'\n\t'
4
+ set -vx
5
+
6
+ bundle install
7
+
8
+ # Do any other automated setup that you need to do here
@@ -0,0 +1,59 @@
1
+ #==============================================================================
2
+ # Copyright (C) 2020-present Alces Flight Ltd.
3
+ #
4
+ # This file is part of FlightFacade.
5
+ #
6
+ # This program and the accompanying materials are made available under
7
+ # the terms of the Eclipse Public License 2.0 which is available at
8
+ # <https://www.eclipse.org/legal/epl-2.0>, or alternative license
9
+ # terms made available by Alces Flight Ltd - please direct inquiries
10
+ # about licensing to licensing@alces-flight.com.
11
+ #
12
+ # FlightFacade is distributed in the hope that it will be useful, but
13
+ # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
14
+ # IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS
15
+ # OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
16
+ # PARTICULAR PURPOSE. See the Eclipse Public License 2.0 for more
17
+ # details.
18
+ #
19
+ # You should have received a copy of the Eclipse Public License 2.0
20
+ # along with FlightFacade. If not, see:
21
+ #
22
+ # https://opensource.org/licenses/EPL-2.0
23
+ #
24
+ # For more information on FlightFacade , please visit:
25
+ # https://github.com/openflighthpc/flight_facade
26
+ #===============================================================================
27
+
28
+ lib = File.expand_path("lib", __dir__)
29
+ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
30
+ require "flight_facade/version"
31
+
32
+ Gem::Specification.new do |spec|
33
+ spec.name = "flight_facade"
34
+ spec.version = FlightFacade::VERSION
35
+ spec.authors = ["Alces Flight Ltd"]
36
+ spec.email = ["flight@openflighthpc.org"]
37
+
38
+ spec.summary = "Provides a colletion of interfaces to cluster concepts"
39
+ spec.homepage = "https://github.com/openflighthpc/flight_facade"
40
+ spec.license = 'EPL-2.0'
41
+
42
+ spec.metadata["homepage_uri"] = spec.homepage
43
+
44
+ spec.files = Dir.chdir(File.expand_path('..', __FILE__)) do
45
+ `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
46
+ end
47
+ spec.bindir = "bin"
48
+ spec.executables = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
49
+ spec.require_paths = ["lib"]
50
+
51
+ spec.add_runtime_dependency "activesupport"
52
+ spec.add_runtime_dependency 'activemodel'
53
+ spec.add_runtime_dependency "hashie"
54
+
55
+ spec.add_development_dependency "bundler", "~> 2.0"
56
+ spec.add_development_dependency "rake", "~> 10.0"
57
+ spec.add_development_dependency "rspec", "~> 3.0"
58
+ spec.add_development_dependency 'pry'
59
+ end
@@ -0,0 +1,31 @@
1
+ #==============================================================================
2
+ # Copyright (C) 2020-present Alces Flight Ltd.
3
+ #
4
+ # This file is part of FlightFacade.
5
+ #
6
+ # This program and the accompanying materials are made available under
7
+ # the terms of the Eclipse Public License 2.0 which is available at
8
+ # <https://www.eclipse.org/legal/epl-2.0>, or alternative license
9
+ # terms made available by Alces Flight Ltd - please direct inquiries
10
+ # about licensing to licensing@alces-flight.com.
11
+ #
12
+ # FlightFacade is distributed in the hope that it will be useful, but
13
+ # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
14
+ # IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS
15
+ # OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
16
+ # PARTICULAR PURPOSE. See the Eclipse Public License 2.0 for more
17
+ # details.
18
+ #
19
+ # You should have received a copy of the Eclipse Public License 2.0
20
+ # along with FlightFacade. If not, see:
21
+ #
22
+ # https://opensource.org/licenses/EPL-2.0
23
+ #
24
+ # For more information on FlightFacade , please visit:
25
+ # https://github.com/openflighthpc/flight_facade
26
+ #===============================================================================
27
+
28
+ require "flight_facade/version"
29
+ require 'flight_facade/models'
30
+ require 'flight_facade/facades'
31
+
@@ -0,0 +1,176 @@
1
+ #==============================================================================
2
+ # Copyright (C) 2020-present Alces Flight Ltd.
3
+ #
4
+ # This file is part of FlightFacade.
5
+ #
6
+ # This program and the accompanying materials are made available under
7
+ # the terms of the Eclipse Public License 2.0 which is available at
8
+ # <https://www.eclipse.org/legal/epl-2.0>, or alternative license
9
+ # terms made available by Alces Flight Ltd - please direct inquiries
10
+ # about licensing to licensing@alces-flight.com.
11
+ #
12
+ # FlightFacade is distributed in the hope that it will be useful, but
13
+ # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
14
+ # IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS
15
+ # OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
16
+ # PARTICULAR PURPOSE. See the Eclipse Public License 2.0 for more
17
+ # details.
18
+ #
19
+ # You should have received a copy of the Eclipse Public License 2.0
20
+ # along with FlightFacade. If not, see:
21
+ #
22
+ # https://opensource.org/licenses/EPL-2.0
23
+ #
24
+ # For more information on FlightFacade , please visit:
25
+ # https://github.com/openflighthpc/flight_facade
26
+ #===============================================================================
27
+
28
+ require 'active_support/concern'
29
+ require 'active_support/core_ext/module/delegation'
30
+ require 'active_support/core_ext/hash'
31
+ require 'hashie'
32
+
33
+ module FlightFacade
34
+ module HasFacade
35
+ extend ActiveSupport::Concern
36
+
37
+ included do
38
+ module self::Base
39
+ extend ActiveSupport::Concern
40
+
41
+ class_methods do
42
+ def method_added(m)
43
+ self.module_parent.eigen_class.delegate(m, to: :facade_instance)
44
+ end
45
+ end
46
+ end
47
+ end
48
+
49
+ class_methods do
50
+ attr_writer :facade_instance
51
+
52
+ def eigen_class
53
+ class << self
54
+ return self
55
+ end
56
+ end
57
+
58
+ def facade_instance
59
+ @facade_instance || raise(NotImplementedError)
60
+ end
61
+
62
+ def define_facade(name, super_class = Object, &b)
63
+ klass = Class.new(super_class)
64
+ self.const_set(name, klass)
65
+ klass.include(self::Base)
66
+ klass.class_exec(&b) if b
67
+ end
68
+ end
69
+ end
70
+
71
+ module GroupFacade
72
+ include HasFacade
73
+
74
+ module Base
75
+ # Query for a Group object by its name alone
76
+ # @param name [String] the name of the group
77
+ # @return [Group] the group object containing the nodes
78
+ # @return [nil] if it could not resolve the name
79
+ def find_by_name(name)
80
+ raise NotImplementedError
81
+ end
82
+
83
+ # Query for all the statically available groups. This method may not
84
+ # include all the ephemeral groups available in `find_by_name`
85
+ #
86
+ # @return [Array<Group>] the list of static groups
87
+ def index_all
88
+ raise NotImplementedError
89
+ end
90
+ end
91
+
92
+ define_facade('Dummy')
93
+
94
+ define_facade('Exploding') do
95
+ EXPLODE_REGEX = /\A(?<leader>[[:alnum:]]+)(\[(?<low>\d+)\-(?<high>\d+)\])?\Z/
96
+ PADDING_REGEX = /0*\Z/
97
+
98
+ def self.explode_names(input)
99
+ parts = input.split(',').reject(&:empty?)
100
+ return nil unless parts.all? { |p| EXPLODE_REGEX.match?(p) }
101
+ parts.map do |part|
102
+ captures = EXPLODE_REGEX.match(part).named_captures.reject { |_, v| v.nil? }
103
+ if captures.key?('low')
104
+ leader = captures['leader']
105
+ max_pads = PADDING_REGEX.match(leader).to_s.length
106
+ stripped_leader = leader.sub(PADDING_REGEX, '')
107
+ low = captures['low'].to_i
108
+ high = captures['high'].to_i
109
+ (low..high).map do |index|
110
+ pads = max_pads - index.to_s.length + 1
111
+ "#{stripped_leader}#{'0' * pads if pads > 0}#{index}"
112
+ end
113
+ else
114
+ part
115
+ end
116
+ end.flatten
117
+ end
118
+
119
+ def find_by_name(name)
120
+ node_names = self.class.explode_names(name)
121
+ return nil if node_names.nil?
122
+ nodes = node_names.map { |n| NodeFacade.find_by_name(n) }.reject(&:nil?)
123
+ Group.new(name: name, nodes: nodes)
124
+ end
125
+
126
+ def index_all
127
+ []
128
+ end
129
+ end
130
+ end
131
+
132
+ module NodeFacade
133
+ include HasFacade
134
+
135
+ module Base
136
+ # Query for a Node object by its name alone
137
+ # @param name [String] the name of the node
138
+ # @return [Node, nil] the node object or nil if it could not resolve the name
139
+ def find_by_name(name)
140
+ raise NotImplementedError
141
+ end
142
+
143
+ # Query for all the available nodes
144
+ # @return [Array<Node>] the list of nodes
145
+ def index_all
146
+ raise NotImplementedError
147
+ end
148
+ end
149
+
150
+ define_facade('Dummy')
151
+
152
+ define_facade('Standalone', Hash) do
153
+ include Hashie::Extensions::MergeInitializer
154
+ include Hashie::Extensions::IndifferentAccess
155
+
156
+ def initialize(*_)
157
+ super
158
+ delete('__meta__')
159
+ end
160
+
161
+ def find_by_name(input)
162
+ name = input.to_s
163
+ return nil unless key?(name)
164
+ data = self[name].symbolize_keys
165
+ ranks = data[:ranks] || []
166
+ params = data.reject { |k, _| k == :ranks }
167
+ Node.new(name: name, params: params, ranks: ranks)
168
+ end
169
+
170
+ def index_all
171
+ keys.map { |k| find_by_name(k) }
172
+ end
173
+ end
174
+ end
175
+ end
176
+
@@ -0,0 +1,71 @@
1
+ #==============================================================================
2
+ # Copyright (C) 2020-present Alces Flight Ltd.
3
+ #
4
+ # This file is part of FlightFacade.
5
+ #
6
+ # This program and the accompanying materials are made available under
7
+ # the terms of the Eclipse Public License 2.0 which is available at
8
+ # <https://www.eclipse.org/legal/epl-2.0>, or alternative license
9
+ # terms made available by Alces Flight Ltd - please direct inquiries
10
+ # about licensing to licensing@alces-flight.com.
11
+ #
12
+ # FlightFacade is distributed in the hope that it will be useful, but
13
+ # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
14
+ # IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS
15
+ # OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
16
+ # PARTICULAR PURPOSE. See the Eclipse Public License 2.0 for more
17
+ # details.
18
+ #
19
+ # You should have received a copy of the Eclipse Public License 2.0
20
+ # along with FlightFacade. If not, see:
21
+ #
22
+ # https://opensource.org/licenses/EPL-2.0
23
+ #
24
+ # For more information on FlightFacade , please visit:
25
+ # https://github.com/openflighthpc/flight_facade
26
+ #===============================================================================
27
+
28
+ require 'hashie'
29
+ require 'active_model'
30
+
31
+ module FlightFacade
32
+ class BaseHashieDashModel
33
+ def self.inherited(klass)
34
+ data_class = Class.new(Hashie::Dash) do
35
+ include Hashie::Extensions::IgnoreUndeclared
36
+ include ActiveModel::Validations
37
+
38
+ def self.method_added(m)
39
+ module_parent.delegate(m, to: :data)
40
+ end
41
+ end
42
+
43
+ klass.const_set('DataHash', data_class)
44
+ klass.delegate(*(ActiveModel::Validations.instance_methods - Object.methods), to: :data)
45
+ end
46
+
47
+ attr_reader :data
48
+
49
+ def initialize(*a)
50
+ @data = self.class::DataHash.new(*a)
51
+ end
52
+ end
53
+
54
+ class Node < BaseHashieDashModel
55
+ DataHash.class_exec do
56
+ include Hashie::Extensions::Dash::PropertyTranslation
57
+
58
+ property :name, required: true
59
+ property :params, required: true
60
+ property :ranks, default: [], transform_with: ->(v) { (v.dup << 'default').uniq }
61
+ end
62
+ end
63
+
64
+ class Group < BaseHashieDashModel
65
+ DataHash.class_exec do
66
+ property :name, required: true
67
+ property :nodes, default: []
68
+ end
69
+ end
70
+ end
71
+
@@ -0,0 +1,30 @@
1
+ #==============================================================================
2
+ # Copyright (C) 2020-present Alces Flight Ltd.
3
+ #
4
+ # This file is part of FlightFacade.
5
+ #
6
+ # This program and the accompanying materials are made available under
7
+ # the terms of the Eclipse Public License 2.0 which is available at
8
+ # <https://www.eclipse.org/legal/epl-2.0>, or alternative license
9
+ # terms made available by Alces Flight Ltd - please direct inquiries
10
+ # about licensing to licensing@alces-flight.com.
11
+ #
12
+ # FlightFacade is distributed in the hope that it will be useful, but
13
+ # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
14
+ # IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS
15
+ # OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
16
+ # PARTICULAR PURPOSE. See the Eclipse Public License 2.0 for more
17
+ # details.
18
+ #
19
+ # You should have received a copy of the Eclipse Public License 2.0
20
+ # along with FlightFacade. If not, see:
21
+ #
22
+ # https://opensource.org/licenses/EPL-2.0
23
+ #
24
+ # For more information on FlightFacade , please visit:
25
+ # https://github.com/openflighthpc/flight_facade
26
+ #===============================================================================
27
+
28
+ module FlightFacade
29
+ VERSION = "0.1.1"
30
+ end
metadata ADDED
@@ -0,0 +1,160 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: flight_facade
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.1.1
5
+ platform: ruby
6
+ authors:
7
+ - Alces Flight Ltd
8
+ autorequire:
9
+ bindir: bin
10
+ cert_chain: []
11
+ date: 2020-02-17 00:00:00.000000000 Z
12
+ dependencies:
13
+ - !ruby/object:Gem::Dependency
14
+ name: activesupport
15
+ requirement: !ruby/object:Gem::Requirement
16
+ requirements:
17
+ - - ">="
18
+ - !ruby/object:Gem::Version
19
+ version: '0'
20
+ type: :runtime
21
+ prerelease: false
22
+ version_requirements: !ruby/object:Gem::Requirement
23
+ requirements:
24
+ - - ">="
25
+ - !ruby/object:Gem::Version
26
+ version: '0'
27
+ - !ruby/object:Gem::Dependency
28
+ name: activemodel
29
+ requirement: !ruby/object:Gem::Requirement
30
+ requirements:
31
+ - - ">="
32
+ - !ruby/object:Gem::Version
33
+ version: '0'
34
+ type: :runtime
35
+ prerelease: false
36
+ version_requirements: !ruby/object:Gem::Requirement
37
+ requirements:
38
+ - - ">="
39
+ - !ruby/object:Gem::Version
40
+ version: '0'
41
+ - !ruby/object:Gem::Dependency
42
+ name: hashie
43
+ requirement: !ruby/object:Gem::Requirement
44
+ requirements:
45
+ - - ">="
46
+ - !ruby/object:Gem::Version
47
+ version: '0'
48
+ type: :runtime
49
+ prerelease: false
50
+ version_requirements: !ruby/object:Gem::Requirement
51
+ requirements:
52
+ - - ">="
53
+ - !ruby/object:Gem::Version
54
+ version: '0'
55
+ - !ruby/object:Gem::Dependency
56
+ name: bundler
57
+ requirement: !ruby/object:Gem::Requirement
58
+ requirements:
59
+ - - "~>"
60
+ - !ruby/object:Gem::Version
61
+ version: '2.0'
62
+ type: :development
63
+ prerelease: false
64
+ version_requirements: !ruby/object:Gem::Requirement
65
+ requirements:
66
+ - - "~>"
67
+ - !ruby/object:Gem::Version
68
+ version: '2.0'
69
+ - !ruby/object:Gem::Dependency
70
+ name: rake
71
+ requirement: !ruby/object:Gem::Requirement
72
+ requirements:
73
+ - - "~>"
74
+ - !ruby/object:Gem::Version
75
+ version: '10.0'
76
+ type: :development
77
+ prerelease: false
78
+ version_requirements: !ruby/object:Gem::Requirement
79
+ requirements:
80
+ - - "~>"
81
+ - !ruby/object:Gem::Version
82
+ version: '10.0'
83
+ - !ruby/object:Gem::Dependency
84
+ name: rspec
85
+ requirement: !ruby/object:Gem::Requirement
86
+ requirements:
87
+ - - "~>"
88
+ - !ruby/object:Gem::Version
89
+ version: '3.0'
90
+ type: :development
91
+ prerelease: false
92
+ version_requirements: !ruby/object:Gem::Requirement
93
+ requirements:
94
+ - - "~>"
95
+ - !ruby/object:Gem::Version
96
+ version: '3.0'
97
+ - !ruby/object:Gem::Dependency
98
+ name: pry
99
+ requirement: !ruby/object:Gem::Requirement
100
+ requirements:
101
+ - - ">="
102
+ - !ruby/object:Gem::Version
103
+ version: '0'
104
+ type: :development
105
+ prerelease: false
106
+ version_requirements: !ruby/object:Gem::Requirement
107
+ requirements:
108
+ - - ">="
109
+ - !ruby/object:Gem::Version
110
+ version: '0'
111
+ description:
112
+ email:
113
+ - flight@openflighthpc.org
114
+ executables:
115
+ - console
116
+ - setup
117
+ extensions: []
118
+ extra_rdoc_files: []
119
+ files:
120
+ - ".gitignore"
121
+ - ".rspec"
122
+ - ".travis.yml"
123
+ - CODE_OF_CONDUCT.md
124
+ - CONTRIBUTING.md
125
+ - Gemfile
126
+ - LICENSE.txt
127
+ - README.md
128
+ - Rakefile
129
+ - bin/console
130
+ - bin/setup
131
+ - flight_facade.gemspec
132
+ - lib/flight_facade.rb
133
+ - lib/flight_facade/facades.rb
134
+ - lib/flight_facade/models.rb
135
+ - lib/flight_facade/version.rb
136
+ homepage: https://github.com/openflighthpc/flight_facade
137
+ licenses:
138
+ - EPL-2.0
139
+ metadata:
140
+ homepage_uri: https://github.com/openflighthpc/flight_facade
141
+ post_install_message:
142
+ rdoc_options: []
143
+ require_paths:
144
+ - lib
145
+ required_ruby_version: !ruby/object:Gem::Requirement
146
+ requirements:
147
+ - - ">="
148
+ - !ruby/object:Gem::Version
149
+ version: '0'
150
+ required_rubygems_version: !ruby/object:Gem::Requirement
151
+ requirements:
152
+ - - ">="
153
+ - !ruby/object:Gem::Version
154
+ version: '0'
155
+ requirements: []
156
+ rubygems_version: 3.0.3
157
+ signing_key:
158
+ specification_version: 4
159
+ summary: Provides a colletion of interfaces to cluster concepts
160
+ test_files: []