falkorlib 0.7.7 → 0.7.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 782eba9178dc316cbad054c36ca3e09396201611
4
- data.tar.gz: 8a5562e36d213fa974b469f4e4376783a897a3a3
3
+ metadata.gz: 554b1778c0f221f9e35a3d07227bb29b731607eb
4
+ data.tar.gz: 684ead60778ae61ae7a4d973b0b12a3e94d7ce8a
5
5
  SHA512:
6
- metadata.gz: a52a8f4d750a0a3f870e9e3295a4cce4e265a8a2e3975361ab28184329eb07f25e2325aaec051f4ad24ffb1271c61333b4c0eebc9c0069a1d8571f45402cc0cb
7
- data.tar.gz: 767523d89c3607c20b5da61a90866ecd8fcfb4583683b931ddb380a5cfa7638105d7fa9b49eb2fcf65993663092627d76c4a18ec04513ea0e4c68cd89ce82df0
6
+ metadata.gz: 32770c26be0b2c664b3ac5a57445e898c628a003895e6ef352fb8ebbf607e85cec326f07f09232e6b4960107c88c209b2938a5d609914586e3eccb947f34a8ec
7
+ data.tar.gz: 5ac8a060f15f35838b390e2709265fc4053635833aee10cb4d156cb72163de6ea988ccc169ac791a309c269df1dbd6914261b103a0169c536f29d63f86b57216
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- falkorlib (0.7.7)
4
+ falkorlib (0.7.8)
5
5
  activesupport (~> 4.0)
6
6
  artii (>= 2.1)
7
7
  awesome_print (~> 1.2)
@@ -70,7 +70,7 @@ begin
70
70
  #t.pattern = "spec/**/common_*.rb"
71
71
  #t.pattern = "spec/**/versioning_*spec.rb"
72
72
  #t.pattern = "spec/**/puppet*spec.rb"
73
- #t.pattern = "spec/**/bootstrap_spec.rb"
73
+ #t.pattern = "spec/**/bootstrap_*spec.rb"
74
74
  #t.pattern = "spec/**/git*spec.rb"
75
75
  #t.pattern = "spec/**/error*spec.rb"
76
76
  #t.pattern = "spec/**/config*spec.rb"
@@ -19,7 +19,7 @@ module FalkorLib #:nodoc:
19
19
  # MAJOR: Defines the major version
20
20
  # MINOR: Defines the minor version
21
21
  # PATCH: Defines the patch version
22
- MAJOR, MINOR, PATCH = 0, 7, 7
22
+ MAJOR, MINOR, PATCH = 0, 7, 8
23
23
 
24
24
  module_function
25
25
 
@@ -3,7 +3,7 @@
3
3
  #########################################
4
4
  # bootstrap_latex_spec.rb
5
5
  # @author Sebastien Varrette <Sebastien.Varrette@uni.lu>
6
- # Time-stamp: <Sun 2016-11-13 21:37 svarrette>
6
+ # Time-stamp: <Thu 2017-08-17 22:28 svarrette>
7
7
  #
8
8
  # @description Check the Bootstrapping operations for LaTeX-based projects
9
9
  #
@@ -1,5 +1,5 @@
1
1
 
2
- ### [Git-flow](https://github.com/nvie/gitflow)
2
+ ### [Git-flow](https://github.com/petervanderdoes/gitflow-avh)
3
3
 
4
4
  The Git branching model for this repository follows the guidelines of
5
5
  [gitflow](http://nvie.com/posts/a-successful-git-branching-model/).
@@ -8,7 +8,7 @@ In particular, the central repository holds two main branches with an infinite l
8
8
  * `<%= FalkorLib::GitFlow.branches(:master) %>`: the *production-ready* branch
9
9
  * `<%= FalkorLib::GitFlow.branches(:develop) %>`: the main branch where the latest developments interviene. This is the *default* branch you get when you clone the repository.
10
10
 
11
- Thus you are more than encouraged to install the [git-flow](https://github.com/nvie/gitflow) extensions following the [installation procedures](https://github.com/nvie/gitflow/wiki/Installation) to take full advantage of the proposed operations. The associated [bash completion](https://github.com/bobthecow/git-flow-completion) might interest you also.
11
+ Thus you are more than encouraged to install the [git-flow](https://github.com/petervanderdoes/gitflow-avh) (AVH Edition, as the traditional one is no longer supported) extensions following the [installation procedures](https://github.com/petervanderdoes/gitflow-avh/wiki/Installation) to take full advantage of the proposed operations. The associated [bash completion](https://github.com/bobthecow/git-flow-completion) might interest you also.
12
12
 
13
13
  ### Releasing mechanism
14
14
 
@@ -14,7 +14,7 @@ _Note_: These examples are translated from the example of Romain Vimont
14
14
  * item 2 in a block
15
15
  - sub item 1
16
16
 
17
- ### More on Blocks
17
+ ### More on Blocks
18
18
 
19
19
  \blockbegin{A First Block}
20
20
 
@@ -93,8 +93,6 @@ This is from [*Mitch Resnick*](https://en.wikipedia.org/wiki/Mitchel_Resnick).
93
93
  > If you learn to read, you can then read to learn.\
94
94
  > If you learn to code, you can then code to learn.[^ted]
95
95
 
96
- [^ted]: \tiny<http://www.ted.com/talks/mitch_resnick_let_s_teach_kids_to_code.html>
97
-
98
96
  Now a step-by-step appearance:
99
97
 
100
98
  > - first
@@ -114,15 +112,15 @@ Then another.
114
112
  Now some formatting:
115
113
 
116
114
  | There exists 2 types of persons:
117
- | those who understand recursivity and
115
+ | those who understand recursivity and
118
116
  | those who don't understand that there exists 2 types of persons:
119
- | those who understand recursivity and
117
+ | those who understand recursivity and
120
118
  | those who don't understand that there exists 2 types of persons:
121
119
  | ...
122
120
 
123
121
 
124
122
 
125
- ### \LaTeX /Beamer Special
123
+ ### \LaTeX /Beamer Special
126
124
 
127
125
  Some elements __do not__ exist in Pandoc Markdown.
128
126
  In this case, you shall simply use \LaTeX.
@@ -135,7 +133,7 @@ That's an alertblock
135
133
  That's an exampleblock
136
134
  \end{exampleblock}
137
135
 
138
- ### Maths \& Tables
136
+ ### Maths \& Tables
139
137
 
140
138
  With some Formulaes:
141
139
 
@@ -211,7 +209,7 @@ Text on the right column
211
209
  Inside a column environment:
212
210
 
213
211
  * the `block` environment raise an error
214
- * instead, use the following commands:
212
+ * instead, use the following commands:
215
213
 
216
214
  ~~~latex
217
215
  \blockbegin{Title}
@@ -222,7 +220,7 @@ Inside a column environment:
222
220
  \columnsend
223
221
 
224
222
  * This allows to use the Markdown syntax **in** the block.
225
- - only required with the `\columnsbegin ... \columnsend` construction
223
+ - only required with the `\columnsbegin ... \columnsend` construction
226
224
 
227
225
 
228
226
  ### Links
@@ -243,5 +241,3 @@ In french
243
241
  See [UL HPC website].
244
242
 
245
243
  [UL HPC website]: http://hpc.uni.lu
246
-
247
-
@@ -1,10 +1,10 @@
1
1
  % =============================================================================
2
- % File: <%= config[:name] %>.tex --
2
+ % File: <%= config[:name] %>.tex --
3
3
  % Author(s): <%= config[:author] %> (<%= config[:mail] %>)
4
- % Time-stamp: <Tue 2015-06-16 09:22 svarrette>
5
- %
4
+ % Time-stamp: <Thu 2017-08-17 22:22 svarrette>
5
+ %
6
6
  % Copyright (c) <%= Time.now.year %> <%= config[:author] %><Sebastien.Varrette@uni.lu>
7
- %
7
+ %
8
8
  % For more information:
9
9
  % - LaTeX: http://www.latex-project.org/
10
10
  % - Beamer: https://bitbucket.org/rivanvx/beamer/
@@ -36,7 +36,9 @@
36
36
  \title{<%= config[:title] %>}
37
37
  \subtitle{<%= config[:subtitle] %>}
38
38
 
39
- \author{<%= config[:author] %>}
39
+ \author[<%= config[:author] %> \& al.]{
40
+ \underline{<%= config[:author] %>}
41
+ }
40
42
  \institute[PCOG Research unit]{
41
43
  Parallel Computing and Optimization Group (\href{http://pcog.uni.lu}{PCOG}),
42
44
  University of Luxembourg (\href{http://www.uni.lu}{UL}), Luxembourg
@@ -64,9 +66,9 @@
64
66
  }
65
67
  }
66
68
 
67
- % ========================
69
+ % ========================
68
70
  \input{_content.md} % Markdown content
69
- % ========================
71
+ % ========================
70
72
 
71
73
  % ======================== END =========================
72
74
  \section*{Thank you for your attention...}
@@ -78,12 +80,11 @@
78
80
  % \emph{Contact}\\
79
81
  {\tiny
80
82
  \emph{<%= config[:author] %>}\\
83
+ ~~~~ \structure{University of Luxembourg, Belval Campus}:\\
84
+ ~~~~ Maison du Nombre, 4th floor\\
85
+ ~~~~ 2, avenue de l'Universit\'e\\
86
+ ~~~~ L-4365 Esch-sur-Alzette\\
81
87
  ~~~~ \textit{mail:} \href{mailto:<%= config[:mail] %>}{<%= config[:mail] %>}\\
82
- ~~~~ Office E-007\\
83
- ~~~~ Campus Kirchberg\\
84
- ~~~~ 6, rue Coudenhove-Kalergi\\
85
- ~~~~ L-1359 Luxembourg
86
-
87
88
  }
88
89
  \column{0.5\textwidth}
89
90
  % \scalebox{8}{\emph{?}}
@@ -114,7 +115,7 @@
114
115
 
115
116
  % ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
116
117
  % eof
117
- %
118
+ %
118
119
  % Local Variables:
119
120
  % mode: latex
120
121
  % mode: flyspell
@@ -1,10 +1,5 @@
1
1
  This Puppet Module has been implemented in the context of the [UL HPC](http://hpc.uni.lu) Platform of the [University of Luxembourg](http://www.uni.lu).
2
- More precisely, the [UL HPC Management Team](https://hpc.uni.lu/about/team.html#system-administrators) took care of this development for this module.
2
+ More precisely, the [UL HPC Team](https://hpc.uni.lu/about/team.html#system-administrators) took care of the development for this module.
3
3
 
4
- You can submit bug / issues / feature request using the [<%= config[:name] %> Puppet Module Tracker](<%= config[:issues_url] %>).
4
+ You can submit bug / issues / feature request using the [<%= config[:name] %> Puppet Module Tracker](<%= config[:issues_url] %>).
5
5
  Alternatively, you can contact them on the following email address: `hpc-sysadmins@uni.lu`
6
-
7
-
8
-
9
-
10
-
@@ -3,9 +3,9 @@ There is a number of pre-requisite programs / framework you shall install to be
3
3
  ### Git Branching Model
4
4
 
5
5
  The Git branching model for this repository follows the guidelines of [gitflow](http://nvie.com/posts/a-successful-git-branching-model/).
6
- In particular, the central repository holds two main branches with an infinite lifetime:
6
+ In particular, the central repository holds two main branches with an infinite lifetime:
7
7
 
8
- * `<%= FalkorLib.config[:gitflow][:branches][:master] %>`: the branch holding tags of the successive releases of this tutorial
8
+ * `<%= FalkorLib.config[:gitflow][:branches][:master] %>`: the branch holding tags of the successive releases of this tutorial
9
9
  * `<%= FalkorLib.config[:gitflow][:branches][:develop] %>`: the main branch where the sources are in a state with the latest delivered development changes for the next release. This is the *default* branch you get when you clone the repository, and the one on which developments will take places.
10
10
 
11
11
  You should therefore install [git-flow](https://github.com/nvie/gitflow), and probably also its associated [bash completion](https://github.com/bobthecow/git-flow-completion).
@@ -27,27 +27,26 @@ The ruby stuff part of this repository corresponds to the following files:
27
27
 
28
28
  ### Repository Setup
29
29
 
30
- Then, to make your local copy of the repository ready to use the [git-flow](https://github.com/nvie/gitflow) workflow and the local [RVM](https://rvm.io/) setup, you have to run the following commands once you cloned it for the first time:
30
+ Then, to make your local copy of the repository ready to use the [git-flow](https://github.com/nvie/gitflow) workflow and the local [RVM](https://rvm.io/) setup, you have to run the following commands once you cloned it for the first time:
31
31
 
32
32
  $> gem install bundler # assuming it is not yet available
33
33
  $> bundle install
34
34
  $> rake -T # To list the available tasks
35
- $> rake setup
35
+ $> rake setup
36
36
 
37
37
  You probably wants to activate the bash-completion for rake tasks.
38
38
  I personnaly use the one provided [here](https://github.com/ai/rake-completion)
39
39
 
40
- Also, some of the tasks are hidden. Run `rake -T -A` to list all of them.
40
+ Also, some of the tasks are hidden. Run `rake -T -A` to list all of them.
41
41
 
42
42
  ### RSpec tests
43
43
 
44
- A set of unitary tests are defined to validate the different function of my library using [Rspec](http://rspec.info/)
44
+ A set of unitary tests are defined to validate the different function of my library using [Rspec](http://rspec.info/)
45
45
 
46
46
  You can run these tests by issuing:
47
47
 
48
48
  $> rake rspec # NOT YET IMPLEMENTED
49
-
50
- By conventions, you will find all the currently implemented tests in the `spec/` directory, in files having the `_spec.rb` suffix. This is expected from the `rspec` task of the `Rakefile`.
51
49
 
52
- **Important** Kindly stick to this convention, and feature tests for all definitions/classes/modules you might want to add.
50
+ By conventions, you will find all the currently implemented tests in the `spec/` directory, in files having the `_spec.rb` suffix. This is expected from the `rspec` task of the `Rakefile`.
53
51
 
52
+ **Important** Kindly stick to this convention, and feature tests for all definitions/classes/modules you might want to add.
@@ -1,5 +1,5 @@
1
1
  The operation consisting of releasing a new version of this repository is
2
- automated by a set of tasks within the `Rakefile`.
2
+ automated by a set of tasks within the `Rakefile`.
3
3
 
4
4
  In this context, a version number have the following format:
5
5
 
@@ -13,7 +13,7 @@ where:
13
13
 
14
14
  Example: `1.2.0`
15
15
 
16
- The current version number is stored in the file `metadata.json`.
16
+ The current version number is stored in the file `metadata.json`.
17
17
  For more information on the version, run:
18
18
 
19
19
  $> rake version:info
@@ -27,4 +27,4 @@ Then, to make the release effective, just run:
27
27
 
28
28
  $> rake version:release
29
29
 
30
- This will finalize the release using `git-flow`, create the appropriate tag and merge all things the way they should be.
30
+ This will finalize the release using `git-flow`, create the appropriate tag and merge all things the way they should be.
@@ -1,11 +1,12 @@
1
1
  -*- mode: markdown; mode: visual-line; -*-
2
2
 
3
- # <%= config[:name] %> Puppet Module
3
+ # <%= config[:name] %> Puppet Module
4
4
 
5
5
  [![Puppet Forge](http://img.shields.io/puppetforge/v/<%= config[:name].gsub(/-/,"/") %>.svg)](<%= config[:forge_url] %>)
6
6
  [![License](http://img.shields.io/:license-<%= config[:license].gsub(/-/, '') %>-blue.svg)](LICENSE)
7
7
  ![Supported Platforms](http://img.shields.io/badge/platform-<%= config[:platforms].join('|') %>-lightgrey.svg)
8
8
  [![Documentation Status](https://readthedocs.org/projects/<%= config[:docs_project] %>/badge/?version=latest)](https://readthedocs.org/projects/<%= config[:docs_project] %>/?badge=latest)
9
+ [![By ULHPC](https://img.shields.io/badge/by-ULHPC-blue.svg)](http://hpc.uni.lu)
9
10
 
10
11
  Copyright (c) <%= Time.now.year %> <%= config[:author] %> <<%= config[:mail] %>>
11
12
 
@@ -19,13 +20,11 @@ This is the main page of the documentation for this Puppet module, which is host
19
20
  It proposes to detail the following elements:
20
21
 
21
22
  * An [Overview](overview.md) of the module is proposed, describing the puppet classes and/or definitions it implements.
22
- - you might also wish to check the `tests/` directory for sample test cases
23
+ - you might also wish to check the `tests/` directory for sample test cases
23
24
  * How to [test this module with Vagrant](vagrant.md)
24
25
  * How to [contribute](contributing/index.md) to this puppet module development. In particular, we detail:
25
26
  - the [directory tree structure](contributing/layout.md)
26
27
  - the steps to follow to [setup this repository](contributing/setup.md)
27
- - information as regard the [semantic versioning](contributing/versioning.md) of this Puppet module.
28
+ - information as regard the [semantic versioning](contributing/versioning.md) of this Puppet module.
28
29
  - Apart form the directory layout, we will cover various configuration aspects ([git-flow](https://github.com/nvie/gitflow), [RVM](https://rvm.io/), [Bundler](http://bundler.io/) etc.)
29
30
  * Details on the [Read the Docs](http://<%= config[:docs_project] %>.readthedocs.org/en/latest/) management.
30
-
31
-
@@ -4,7 +4,7 @@
4
4
 
5
5
  The best way to test this module in a non-intrusive way is to rely on [Vagrant](http://www.vagrantup.com/).
6
6
  [Vagrant](http://vagrantup.com/) uses [Oracle's VirtualBox](http://www.virtualbox.org/)
7
- to build configurable, lightweight, and portable virtual machines dynamically.
7
+ to build configurable, lightweight, and portable virtual machines dynamically.
8
8
 
9
9
  * [Reference installation notes](http://docs.vagrantup.com/v2/installation/) -- assuming you have installed [Oracle's VirtualBox](http://www.virtualbox.org/)
10
10
  * [installation notes on Mac OS](http://sourabhbajaj.com/mac-setup/Vagrant/README.html) using [Homebrew](http://brew.sh/) and [Cask](http://sourabhbajaj.com/mac-setup/Homebrew/Cask.html)
@@ -13,17 +13,19 @@ The `Vagrantfile` at the root of the repository pilot the provisioning of many v
13
13
 
14
14
  You can list the available vagrant box as follows:
15
15
 
16
- $> vagrant status
17
- Current machine states:
16
+ ```bash
17
+ $> vagrant status
18
+ Current machine states:
18
19
 
19
- centos-7 not created (virtualbox)
20
+ centos-7 not created (virtualbox)
20
21
  debian-7 not created (virtualbox)
21
22
 
22
23
  This environment represents multiple VMs. The VMs are all listed
23
24
  above with their current state. For more information about a specific
24
25
  VM, run `vagrant status NAME`.
26
+ ```
25
27
 
26
- As suggested, you can run a debian 7 machine for instance by issuing:
28
+ As suggested, you can run a debian 7 machine for instance by issuing:
27
29
 
28
30
  $> vagrant up debian-7
29
31
 
@@ -35,7 +37,7 @@ When you run `vagrant up <os>` to boot the VM, it is configured to be provisione
35
37
  This script is responsible for two main tasks:
36
38
 
37
39
  1. pre-install the puppet modules listed as dependencies in `metadata.json`
38
- 2. make the appropriate symbolic link in the puppet module directory (to `/vagrant`) to ensure you can directly make changes and correct your own module transparently within the box.
40
+ 2. make the appropriate symbolic link in the puppet module directory (to `/vagrant`) to ensure you can directly make changes and correct your own module transparently within the box.
39
41
 
40
42
  So you can test the manifests of the `tests/` directory within the VM:
41
43
 
@@ -43,7 +45,7 @@ So you can test the manifests of the `tests/` directory within the VM:
43
45
  [...]
44
46
  (vagrant)$> sudo puppet apply -t /vagrant/tests/init.pp
45
47
 
46
- From now on, you can test (with --noop) the other manifests.
48
+ From now on, you can test (with --noop) the other manifests.
47
49
 
48
50
  Run `vagrant halt` (or `vagrant destroy`) to stop (or kill) the VM once you've finished to play with it.
49
51
 
@@ -4,7 +4,7 @@
4
4
  # License:: <%= config[:license].capitalize %>
5
5
  #
6
6
  # ------------------------------------------------------------------------------
7
- # = Defines: <%= config[:shortname] %>::mydef
7
+ # == Defines: <%= config[:shortname] %>::mydef
8
8
  #
9
9
  # <%= config[:summary] %>
10
10
  #
@@ -43,9 +43,7 @@
43
43
  # == Warnings
44
44
  #
45
45
  # /!\ Always respect the style guide available
46
- # here[http://docs.puppetlabs.com/guides/style_guide]
47
- #
48
- # [Remember: No empty lines between comments and class definition]
46
+ # here[https://docs.puppet.com/puppet/latest/style_guide.html]
49
47
  #
50
48
  define <%= config[:shortname] %>::mydef(
51
49
  $ensure = 'present',
@@ -53,6 +51,15 @@ define <%= config[:shortname] %>::mydef(
53
51
  $source = ''
54
52
  )
55
53
  {
54
+ validate_re($ensure, '^present$|^absent$')
55
+ #validate_string($mode)
56
+ #validate_hash($hash)
57
+ #validate_absolute_path($path)
58
+ #if ! (is_string($owner) or is_integer($owner)) {
59
+ # fail("\$owner must be a string or integer, got ${owner}")
60
+ #}
61
+ #validate_bool($replace)
62
+
56
63
  include <%= config[:shortname] %>::params
57
64
 
58
65
  # $name is provided at define invocation
@@ -106,6 +113,3 @@ define <%= config[:shortname] %>::mydef(
106
113
  # }
107
114
 
108
115
  }
109
-
110
-
111
-
@@ -30,27 +30,20 @@ class <%= config[:shortname] %>::params {
30
30
  ###########################################
31
31
 
32
32
  # ensure the presence (or absence) of <%= config[:shortname] %>
33
- $ensure = $::<%= config[:shortname] %>_ensure ? {
34
- '' => 'present',
35
- default => $::<%= config[:shortname] %>_ensure
36
- }
33
+ $ensure = 'present'
37
34
 
38
35
  # The Protocol used. Used by monitor and firewall class. Default is 'tcp'
39
- $protocol = $::<%= config[:shortname] %>_protocol ? {
40
- '' => 'tcp',
41
- default => $::<%= config[:shortname] %>_protocol},
42
- }
36
+ $protocol = 'tcp'
37
+
43
38
  # The port number. Used by monitor and firewall class. The default is 22.
44
- $port = $::<%= config[:shortname] %>_port ? {
45
- '' => 22,
46
- default => $::<%= config[:shortname] %>_port,
47
- }
48
- # example of an array variable
49
- $array_variable = $::<%= config[:shortname] %>_array_variable ? {
50
- '' => [],
51
- default => $::<%= config[:shortname] %>_array_variable,
52
- }
39
+ $port = 22
40
+
41
+ # example of an array/hash variable
42
+ $array_variable = []
43
+ $hash_variable = {}
53
44
 
45
+ # undef variable
46
+ $undefvar = undef
54
47
 
55
48
  #### MODULE INTERNAL VARIABLES #########
56
49
  # (Modify to adapt to unsupported OSes)
@@ -148,4 +141,3 @@ class <%= config[:shortname] %>::params {
148
141
 
149
142
 
150
143
  }
151
-
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: falkorlib
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.7.7
4
+ version: 0.7.8
5
5
  platform: ruby
6
6
  authors:
7
7
  - Sebastien Varrette
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2017-04-04 00:00:00.000000000 Z
11
+ date: 2017-08-17 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rake