Skip to content

Commit 392cfe9

Browse files
alvagantealvagante
committed
Updates
1 parent e85cc60 commit 392cfe9

File tree

8 files changed

+111
-6208
lines changed

8 files changed

+111
-6208
lines changed

‎_includes/blog_detail.html‎

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,17 @@
11
<section id="blogs">
22
<div class="content-section-a">
33
<div class="container">
4+
<div class="row">
5+
<div class="col-lg-4">
6+
<a href="{{ site.url }}/blog/">example42's blog</a></h2>
7+
{{ post.date | date: "%Y-%m-%d" }}
8+
</div>
9+
<div class="col-lg-8">
10+
<h1>{{ page.title }}</h1>
11+
</div>
12+
</div>
413
<div class="row">
514
<div class="col-lg-12">
6-
<h2>{{ page.title }}</h2>
715
{% if page.update_post and page.update_url %}
816
<h4>Update: <a href="{{ page.update_url}}">{{ page.update_post }}</a></h4>
917
{% endif %}

‎_includes/home_blog.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<div class="row">
55
<div class="col-lg-6 col-sm-6">
66
<div class="clearfix"></div>
7-
<h2 class="section-heading">example42's blog</h2>
7+
<h2 class="section-heading"><a href="{{ site.url }}/blog/">example42's blog</a></h2>
88
<div class="lead">
99
<ul class="posts">
1010
{% for post in site.posts limit:8 %}

‎_includes/home_podcast.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<div class="row">
55
<div class="col-lg-6 col-lg-offset-1 col-sm-push-6 col-sm-6">
66
<div class="clearfix"></div>
7-
<h2 class="section-heading">Abnormal DevOps Iterations</h2>
7+
<h2 class="section-heading"><a href="{{ site.url }}/AbnormalDevOpsIterations/">Abnormal DevOps Iterations</a></h2>
88
<div class="lead">
99
A podcast with thought leaders, personalities and founders of the DevOps and Open Source community.</br>
1010
Released weekly on:</br>

‎_includes/home_services.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<div class="row">
55
<div class="col-lg-5 col-lg-offset-1 col-sm-push-6 col-sm-6">
66
<div class="clearfix"></div>
7-
<h2 class="section-heading">Puppet Consulting Services</h2>
7+
<h2 class="section-heading"><a href="{{ site.url }}/services/">Puppet Consulting Services</a></h2>
88
<div class="lead">
99
<ul>
1010
<li><b>Emergency Puppet Support</b> for quick support in a Puppet crisis</li>

‎_includes/services_ansible.html‎

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
<section id="splash">
2+
<div class="content-section-a">
3+
<div class="container">
4+
<div class="row">
5+
<div class="col-lg-12">
6+
<div class="intro-message">
7+
<h1>Ansible <-> Puppet migrations</h1>
8+
<h2>IaC and systems expertise </br>to migrate from one tool to another</h2>
9+
10+
<h3>What is covered:</h3>
11+
<div class="lead">
12+
Even if example42 experience is mainly on Puppet, we can help you in migrating from Puppet to Ansible, or vice versa, leveraging our experience in Infrastructure as Cose, systems management ini mission critical environments. We can support you in:
13+
<ul>
14+
<li>Understanding the differences between Puppet and Ansible</li>
15+
<li>Assessing the complexity of the migration</li>
16+
<li>Planning the migration</li>
17+
<li>Executing the migration</li>
18+
<li>Training your team on the new tool</li>
19+
</ul>
20+
</div>
21+
22+
<h3>How it works:</h3>
23+
<div class="lead">
24+
Our approach is based on a mix of remote and on site activities, with a strong focus on knowledge transfer and operations safety. We will:
25+
<ul>
26+
<li>Start with a brief call to understand your needs and to schedule the consulting activities</li>
27+
<li>During the consulting activities we will work together to plan and execute the migration</li>
28+
<li>We usually follow a step by step approach, focusing on tested and safe implementation of changes</li>
29+
</ul>
30+
</div>
31+
32+
<h3>Why it's worth:</h3>
33+
<div class="lead">
34+
<ul>
35+
<li>Experience: We have already done migrations in both sides</li>
36+
<li>Expertise: Alessandro has vast experience in Puppet software and IT and Cloud operations</li>
37+
<li>Flexibility: If it fits the calendar, we can start at any time. Worldwide.</li>
38+
<li>Efficiency: We focus on the problem. No paper works, tickets, unnecessary communications.</li>
39+
<li>Knowledge transfer: Whatever is done is shared and explained to customer</li>
40+
</ul>
41+
</div>
42+
</div>
43+
</div>
44+
</div>
45+
</div>
46+
</div>
47+
</section>

‎_includes/services_health.html‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
<section id="splash">
2+
<div class="content-section-a">
3+
<div class="container">
4+
<div class="row">
5+
<div class="col-lg-12">
6+
<div class="intro-message">
7+
<h1>Puppet Health Check</h1>
8+
<h2>Am holistic review of your Puppet setup:</br>Infrastructure, code, performance, update status</h2>
9+
10+
<h3>What is covered:</h3>
11+
<div class="lead">
12+
An interactive, live, methodic check up of different components of your Puppet software infrastructure:
13+
<ul>
14+
<li>The current <strong>Puppet reports</strong> to review how errors or recurrent changes can be fixed.</li>
15+
<li>Your <strong>codebase organization</strong> and fit</li>
16+
<li>Deeper <strong>review</strong> of your classes and profiles highlighting parts that can be problematic or can be optimized.</li>
17+
<li>The Puppet <strong>servers' logs</strong>, explaining and reviewing how to solve errors or warnings.</li>
18+
<li><strong>Automated check and lint</strong> of the code base.</li>
19+
<li>We collect data together about code and infrastructure that can be <strong>statically analyzed</strong>.</li>
20+
<li>Review your current <strong>Puppet Development workflow</strong> and eventual suggestions for improvements.</li>
21+
</ul>
22+
</div>
23+
24+
<h3>How it works:</h3>
25+
<div class="lead">
26+
<ul>
27+
<li>We start with a <strong>brief call</strong> to understand your needs and to schedule the consulting activities.</li>
28+
<li>During the consulting activities we will <strong>work together</strong> to review your Puppet setup and to provide guidance on how to fix issues and improve your Puppet code and infrastructure.</li>
29+
<li>At the end of the consulting activities we provide and discuss a <strong>report</strong>, which goes beyond simple syntax and lint checks, and provides practical solutions and suggestions on how to modernize and optimize your Puppet code and infrastructure.</li>
30+
<li>Interactive sessions are intended also as a <strong>training</strong> to better understand your Puppet setup and the metrics that influence its sanity and performance.</li>
31+
</ul>
32+
</div>
33+
34+
<h3>Why it's worth:</h3>
35+
<div class="lead">
36+
Our Puppet Health Check is a cost-effective way to get expert advice on how to fix your Puppet setup and to improve your Puppet code and infrastructure.
37+
<ul>
38+
<li><strong>Expertise</strong>: Alessandro has vast experience in Puppet software and IT and Cloud operations</li>
39+
<li><strong>Flexibility</strong>: If it fits the calendar, we can start at any time. Worldwide.</li>
40+
<li><strong>Efficiency</strong>: We focus on the problem. No paper works, tickets, unnecessary communications.</li>
41+
<li><strong>Knowledge transfer</strong>: Whatever is done is shared and explained to customer</li>
42+
<li><strong>Open source</strong>: We release as open source our Puppet modules and code</li>
43+
<li><strong>Value for money</strong>: The time you will save and the value you get repay the cost multiple times.</li>
44+
</ul>
45+
</div>
46+
</div>
47+
</div>
48+
</div>
49+
</div>
50+
</div>
51+
</section>

0 commit comments

Comments
 (0)