EN Ikoula wiki - User contributions [en]

Template:Backup

2015-10-23T09:26:53Z

Elocart87fda: Created page with "[https://express.ikoula.com/en/idera backup]"

[https://express.ikoula.com/en/idera backup]

How to change my reverse DNS ?

2015-10-23T08:27:20Z

Elocart87fda:

== How to change the DNS reverse of my dedicaced server ? ==
=== You can change your DNS reverse from the extranet :===

#Connect to the [https://extranet.ikoula.com extranet]
#Select the category of server :
[[File:reverse_dns_01.png]]
#Select server :
[[File:reverse_dns_02.png]]
#Select '''REVERSE DNS'' :
[[File:reverse_dns_03.png]]
#Click '''edit'''(1), enter the reverse DNS (2) then click '''Apply'''
[[File:reverse_dns_04.png]]

<div style="background-color: #FF9999;"> Like any DNS change, replication can take up to 72 hours worldwide.</div>

A few useful elements for a verification of the integrity of its system under Windows

2015-10-19T09:49:11Z

Elocart87fda:

<span data-link_translate_de_title="Ein paar nützliche Elemente für eine Überprüfung der Integrität seines Systems unter Windows" data-link_translate_de_url="Ein+paar+n%C3%BCtzliche+Elemente+f%C3%BCr+eine+%C3%9Cberpr%C3%BCfung+der+Integrit%C3%A4t+seines+Systems+unter+Windows">[[:de:Ein paar nützliche Elemente für eine Überprüfung der Integrität seines Systems unter Windows]][[de:Ein paar nützliche Elemente für eine Überprüfung der Integrität seines Systems unter Windows]]
<span data-link_translate_nl_title="Een paar nuttige elementen voor een verificatie van de integriteit van het systeem onder Windows" data-link_translate_nl_url="Een+paar+nuttige+elementen+voor+een+verificatie+van+de+integriteit+van+het+systeem+onder+Windows">[[:nl:Een paar nuttige elementen voor een verificatie van de integriteit van het systeem onder Windows]][[nl:Een paar nuttige elementen voor een verificatie van de integriteit van het systeem onder Windows]]
<span data-link_translate_it_title="Alcuni elementi utili per una verifica dell'integrità del suo sistema sotto Windows" data-link_translate_it_url="Alcuni+elementi+utili+per+una+verifica+dell%27integrit%C3%A0+del+suo+sistema+sotto+Windows">[[:it:Alcuni elementi utili per una verifica dell'integrità del suo sistema sotto Windows]][[it:Alcuni elementi utili per una verifica dell'integrità del suo sistema sotto Windows]]
<span data-link_translate_pt_title="Alguns elementos úteis para uma verificação da integridade do seu sistema sob Windows" data-link_translate_pt_url="Alguns+elementos+%C3%BAteis+para+uma+verifica%C3%A7%C3%A3o+da+integridade+do+seu+sistema+sob+Windows">[[:pt:Alguns elementos úteis para uma verificação da integridade do seu sistema sob Windows]][[pt:Alguns elementos úteis para uma verificação da integridade do seu sistema sob Windows]]
<span data-link_translate_es_title="Algunos elementos útiles para una verificación de la integridad de su sistema bajo Windows" data-link_translate_es_url="Algunos+elementos+%C3%BAtiles+para+una+verificaci%C3%B3n+de+la+integridad+de+su+sistema+bajo+Windows">[[:es:Algunos elementos útiles para una verificación de la integridad de su sistema bajo Windows]][[es:Algunos elementos útiles para una verificación de la integridad de su sistema bajo Windows]]
<span data-link_translate_fr_title="Quelques éléments utiles pour une vérification de l'intégrité de son système sous Windows" data-link_translate_fr_url="Quelques_%C3%A9l%C3%A9ments_utiles_pour_une_v%C3%A9rification_de_l%27int%C3%A9grit%C3%A9_de_son_syst%C3%A8me_sous_Windows">[[:fr:Quelques éléments utiles pour une vérification de l'intégrité de son système sous Windows]][[fr:Quelques éléments utiles pour une vérification de l'intégrité de son système sous Windows]]
 

This article has been created by an automatic translation software. You can view the article source [[:fr:Quelques éléments utiles pour une vérification de l'intégrité de son système sous Windows|here]]. 

== Introduction ==
Secure its server is a task that proves to be long and complex. Updating its operating system and the various components of it is a critical first step, but if you have doubts about the integrity of your system, you will find below some elements allowing you to establish a first rapid diagnostic.

For each point of this tutorial, you will find different information about the checks that are performed as well as some useful commands in conjunction with these.

== Important point ==
The verification of the integrity of the system is time-consuming and complicated.
This article has no to claim to be a tutorial of reference in the field. Also note that following this article will in no way ensure total security, far away but it's a starting point.
He is simply here to present a comprehensive approach accessible to perform a quick check of the integrity of your system.
For further verification, you can turn to the command of a one-time outsourcing (contact our support first ).

== A watchword : prudence ==
Before going further, a reminder is necessary : be careful in your changes, perform backups, rename the files rather than deleting, etc .
Ikoula assumes no liability for the incorrect application of this article.

== Checks file system ==
=== Event Viewer ===
Lots of information is available through this interface and this provides a useful source of information.
You can access it quickly from start > Run > eventvwr.

The graphical interface of event viewer is convenient to implement different filters and easily find an error, a warning, etc. |

Be aware that it can be also practical and quick to exploit the different entries in the event viewer through PowerShell with the cmdlet ''EventLog''.

For example, you can filter on a specific ID via the command :
<syntaxhighlight lang="powershell">
Get-EventLog -LogName System | where {$_.EventID -eq 1074}
</syntaxhighlight>

=== Scheduled tasks ===
It may be interesting to conduct an audit at the level of also scheduled tasks.

Indeed a call to a script or any other element at regular intervals or following various system events can be a good thing.

To verify the different scheduled tasks configured on your system, you can use the graphical utility ''schtasks'' via start > Run > taskschd.msc /s

This utility is also available from a DOS prompt with taskschd.exe.

Just like event viewer, you can also operate the tasks scheduled through the PowerShell language. You can find more information about the cmdlets that are available on microsoft's website by following this link : [https://technet.microsoft.com/en-us/library/jj649816(v=wps.630).aspx https://TechNet.Microsoft.com/en-us/library/jj649816(v=WPS.630).aspx].

=== The programmes launched at startup ===
Some programs or scripts are called at the inception of the system. These can be also easily identified through the utility ''Msconfig '' You can start from start > Execute.

=== Services ===
Services can also be used to initiate an unwanted program.
Different methods are available to consult :
* through a graphical interface with services.msc
* through a DOS prompt with the command ''net start''.

=== Users ===
You can verify that a junk user does not have an account to access your server by listing the different accounts created on the machine.
There again, you have two possibilities :
* a graphical interface is available via start > Run > lusrmgr
* an executable that you can run from a DOS command prompt by typing the command ''NET users ''.

=== The process now started ===
Another check is to list the processes currently launched on your system.
The most obvious to list these processes is the Task Manager (taskmgr ).
You can also list the active processes from a DOS command prompt by performing a WMI query via the following command :
<syntaxhighlight lang="dos">
wmic process list full
</syntaxhighlight>

=== The verification of the signatures of the files systems ===
Windows natively integrates a file signature verification utility. This tool is available through the executable ''Sigverif.exe ''.

A log file will be created and will allow you to view the different information that are subject to verification of the system files analyzed by ''Sigverif '' :
<pre>
********************************

Microsoft Signature Verification

Log file generated on 16/10/2015 at 14:15
OS Platform: Windows (x64), Version: 6.3, Build: 9600, CSDVersion:
Scan Results: Total Files: 62, Signed: 62, Unsigned: 0, Not Scanned: 0

File Modified Version Status Catalog Signed By
------------------ ------------ ----------- ------------ ----------- -------------------
[c:\windows\system32]
streamci.dll 29/10/2014 2:5.1 Signed Package_1894_for_KB3Microsoft Windows
vmbuspipe.dll 29/10/2014 2:5.1 Signed Package_554_for_KB30Microsoft Windows
vmbusres.dll 22/08/2013 2:5.1 Signed Package_554_for_KB30Microsoft Windows
vmdcoinstall.dll 29/10/2014 2:5.1 Signed Package_556_for_KB30Microsoft Windows
vmstorfltres.dll 22/08/2013 2:5.1 Signed Package_556_for_KB30Microsoft Windows
...
</pre>

=== The Microsoft Baseline Security Analyzer tool ===
Microsoft also provides a utility called Microsoft Baseline Security Analyzer (often shortened to the acronym MBSA ) You'll find at the following address : [https://technet.microsoft.com/fr-fr/security/cc184924.aspx https://TechNet.Microsoft.com/fr-FR/security/cc184924.aspx].

This third-party application performs a number of checks on your system i.e. Windows updates (installed, missing, the Automatic Updates settings, etc.) the settings entered for Internet Explorer (areas, security settings, etc.), IIS, SQL Server, Windows Firewall, user accounts, and many other things.

== Audits network ==
=== The HOST file ===
The HOST file located in the directory ''System32\Dritowards \etc\hosts'' may also have been modified in order to shunt the DNS resolution for access to a remote host.
By modifying this file, for example, to point the domain name server with the IP address zzz.fr 1.1.1.1 vers 2.2.2.2 almost seamlessly and thus being robbed of its data, thinking that you can visit the site hosted on the server with the IP address 1.1.1.1

=== DNS servers ===
The use of DNS servers that are not said "trusted " can you also run a risk. You can install your own DNS server if you do not trust third party DNS servers if you wish.
You can list the DNS servers currently used on your system through the command ''ipconfig /all'' but also via the command ''ipconfig /displaydns''

=== Processes and the associated connections ===
You can also see what processes are currently running and the connections that are associated with these processes.

For details, you can run the command ''netstat -naob'' from a DOS command prompt.

You can also update this information every X seconds by adding this time of updating at the end of the command :
<syntaxhighlight lang="dos">
netstat -naob X
</syntaxhighlight>

== External tools ==
Many native tools can bring you help to inspect the integrity of your system.
However, some of them are usable from a DOS command prompt and what makes the reading of the information returned little readable.

You can therefore use third-party tools, and some of them are more suitable as those offered for free by Sysinternals.

For more information, please visit the associated website : [https://technet.microsoft.com/fr-fr/sysinternals/bb545021.aspx https://TechNet.Microsoft.com/fr-FR/Sysinternals/bb545021.aspx].

== Conclusion ==
You now have additional information to perform an initial analysis of your system. Having this information is not the hardest, the exploitation of this information is that there are more complex because you have to be familiar with the various processes system, their ports and different connections associated with.

[[Category:Dedicated_server]]
[[Category:Windows]]
 
<comments />

A few useful elements for a verification of the integrity of its system under Linux

2015-10-19T09:45:41Z

Elocart87fda:

<span data-link_translate_de_title="Ein paar nützliche Elemente für eine Überprüfung der Integrität seines Systems unter Linux" data-link_translate_de_url="Ein+paar+n%C3%BCtzliche+Elemente+f%C3%BCr+eine+%C3%9Cberpr%C3%BCfung+der+Integrit%C3%A4t+seines+Systems+unter+Linux">[[:de:Ein paar nützliche Elemente für eine Überprüfung der Integrität seines Systems unter Linux]][[de:Ein paar nützliche Elemente für eine Überprüfung der Integrität seines Systems unter Linux]]
<span data-link_translate_nl_title="Een paar nuttige elementen voor een verificatie van de integriteit van het systeem onder Linux" data-link_translate_nl_url="Een+paar+nuttige+elementen+voor+een+verificatie+van+de+integriteit+van+het+systeem+onder+Linux">[[:nl:Een paar nuttige elementen voor een verificatie van de integriteit van het systeem onder Linux]][[nl:Een paar nuttige elementen voor een verificatie van de integriteit van het systeem onder Linux]]
<span data-link_translate_it_title="Alcuni elementi utili per una verifica dell'integrità del suo sistema sotto Linux" data-link_translate_it_url="Alcuni+elementi+utili+per+una+verifica+dell%27integrit%C3%A0+del+suo+sistema+sotto+Linux">[[:it:Alcuni elementi utili per una verifica dell'integrità del suo sistema sotto Linux]][[it:Alcuni elementi utili per una verifica dell'integrità del suo sistema sotto Linux]]
<span data-link_translate_pt_title="Alguns elementos úteis para uma verificação da integridade do seu sistema sob Linux" data-link_translate_pt_url="Alguns+elementos+%C3%BAteis+para+uma+verifica%C3%A7%C3%A3o+da+integridade+do+seu+sistema+sob+Linux">[[:pt:Alguns elementos úteis para uma verificação da integridade do seu sistema sob Linux]][[pt:Alguns elementos úteis para uma verificação da integridade do seu sistema sob Linux]]
<span data-link_translate_es_title="Algunos elementos útiles para una verificación de la integridad de su sistema bajo Linux" data-link_translate_es_url="Algunos+elementos+%C3%BAtiles+para+una+verificaci%C3%B3n+de+la+integridad+de+su+sistema+bajo+Linux">[[:es:Algunos elementos útiles para una verificación de la integridad de su sistema bajo Linux]][[es:Algunos elementos útiles para una verificación de la integridad de su sistema bajo Linux]]
<span data-link_translate_fr_title="Quelques éléments utiles pour une vérification de l'intégrité de son système sous Linux" data-link_translate_fr_url="Quelques_%C3%A9l%C3%A9ments_utiles_pour_une_v%C3%A9rification_de_l%27int%C3%A9grit%C3%A9_de_son_syst%C3%A8me_sous_Linux">[[:fr:Quelques éléments utiles pour une vérification de l'intégrité de son système sous Linux]][[fr:Quelques éléments utiles pour une vérification de l'intégrité de son système sous Linux]]
 

This article has been created by an automatic translation software. You can view the article source [[:fr:Quelques éléments utiles pour une vérification de l'intégrité de son système sous Linux|here]]. 

== Introduction ==
Secure its server is a task that proves to be long and complex. Updating its operating system and the various components of it is a critical first step, but if you have doubts about the integrity of your system, you will find below some elements allowing you to establish a first rapid diagnostic.

For each point of this tutorial, you will find different information about the checks that are performed as well as some useful commands in conjunction with these.

== Important point ==
The verification of the integrity of the system is time-consuming and complicated.
This article has no to claim to be a tutorial of reference in the field. Also note that following this article will in no way ensure total security, far away but it's a starting point.
He is simply here to present a comprehensive approach accessible to perform a quick check of the integrity of your system.
For further verification, you can turn to the command of a one-time outsourcing (contact our support first ).

== A watchword : prudence ==
Before going further, a reminder is necessary : be careful in your changes, perform backups, rename the files rather than deleting, etc.
Ikoula assumes no liability for the incorrect application of this article.

== Checks file system ==
=== The various logs ===
Lots of information is available through the newspapers available in ''/var/log/''.

Files that can provide you with valuable information are :
* ''auth.log'' for different connections to your server in SSH
* ''syslog'' for the system logs
* the log files associated with the installed applications (''mail.err'', ''mail.info'', ''mail.err'' for mails, ''fail 2ban.log'' for fail 2ban, etc..)

=== Scheduled tasks ===
It may be interesting to conduct an audit at the level of also scheduled tasks.

Indeed a call to a script or any other element at regular intervals or following various system events can be a good thing.

To verify the different scheduled tasks configured on your system, you can use the more command /etc/crontab

Alternatively, you can use the ls command /etc/cron.* In addition to those cited above to list the different cron in place on your system.

=== Services launched at startup ===
Some programs or scripts are called at the inception of the system. These can be also easily identified through the following command :
<syntaxhighlight lang="bash">
for i in `find /etc/rc*.d -name S*`; do basename $i | sed -r 's/^S[0-9]+//'; done | sort | uniq
</syntaxhighlight>

=== Users ===
You can verify that a junk user does not have an account to access your server by listing the different accounts created on the machine.
The command "cat /etc/passwd" you will identify users with the possibility of using bash on your system.

=== The process now started ===
Another check is to list the processes currently launched on your system.
You can list the active processes via the command :
<syntaxhighlight lang="bash">
ps faux
</syntaxhighlight>

=== The verification of the signatures of installed packages ===
You can verify the signatures on md 5 packages installed on your system using ''debsums''. This package is not installed by default, you need to install it using the command :
<syntaxhighlight lang="bash">
apt-get install debsums
</syntaxhighlight>

Depending on the installed packages and the power of your machine, this can be relatively long. Especially if you use the option ''-a'' which also checks the configuration files.

The verification of the contents of the file sources.list (sources of the different packages that you will install ) maybe also a good thing : ''cat /etc/apt/sources.list''

== Audits network ==
=== The HOST file ===
The HOST file located in ''cat /etc/hosts'' may also have been modified in order to shunt the DNS resolution for access to a remote host.
By modifying this file, for example, to point the domain name server with the IP address zzz.fr 1.1.1.1 towards 2.2.2.2 almost seamlessly and thus being robbed of its data, thinking that you can visit the site hosted on the server with the IP address 1.1.1.1

=== DNS servers ===
The use of DNS servers that are not said "trusted " can you also run a risk. You can install your own DNS server if you do not trust third party DNS servers if you wish.
You can list the DNS servers currently used on your system through the command ''cat /etc/resolv.conf''.

=== Processes and the associated connections ===
You can also see what processes are currently running and the connections that are associated with these processes.

For details, you can run the command ''lsof -Ki''.

You can also update this information every X seconds by adding this time of updating at the end of the command :
<syntaxhighlight lang="bash">
watch -n X lsof -Ki
</syntaxhighlight>

== Conclusion ==
You now have additional information to perform an initial analysis of your system. Having this information is not the hardest, the exploitation of this information is that there are more complex because you have to be familiar with the various processes system, their ports and different connections associated with.

[[Category:Dedicated_server]]
[[Category:Linux]]
 
<comments />

Features of Hosted Exchange 2010

2015-09-29T09:26:16Z

Elocart87fda:

[[:fr:Fonctionnalités d'Hosted Exchange 2010]][[fr:Fonctionnalités d'Hosted Exchange 2010]]
 

This article has been created by an automatic translation software. You can view the article source [[:fr:Fonctionnalités d'Hosted Exchange 2010|here]]. 

'''''What are the features of Hosted Exchange 2010 ?'''''

A description of the features of Hosted Exchange 2010 is available on the following link : [https://www.ikoula.com/portals/0/Ex10-fr-presentation.zip Ex10-en - presentation.zip]

We also transmit this document white label so you customize them to your corporate colours.

Contact our sales department to the 0890 710 712.

More info : [https://www.ex10.biz/fr/manager_ex10 Manager EX10]

[[Category:Hosted_Exchange]]
<comments />

Features of Hosted Exchange 2010

2015-09-29T09:26:04Z

Elocart87fda:

[[Fonctionnalités d'Hosted Exchange 2010]][[fr:Fonctionnalités d'Hosted Exchange 2010]]
 

This article has been created by an automatic translation software. You can view the article source [[:fr:Fonctionnalités d'Hosted Exchange 2010|here]]. 

'''''What are the features of Hosted Exchange 2010 ?'''''

A description of the features of Hosted Exchange 2010 is available on the following link : [https://www.ikoula.com/portals/0/Ex10-fr-presentation.zip Ex10-en - presentation.zip]

We also transmit this document white label so you customize them to your corporate colours.

Contact our sales department to the 0890 710 712.

More info : [https://www.ex10.biz/fr/manager_ex10 Manager EX10]

[[Category:Hosted_Exchange]]
<comments />

Features of Hosted Exchange 2010

2015-09-29T09:20:08Z

Elocart87fda:

Features of Hosted Exchange 2010

2015-09-29T09:19:47Z

Elocart87fda:

[:fr:Fonctionnalités d'Hosted Exchange 2010][[fr:Fonctionnalités d'Hosted Exchange 2010]]
 

This article has been created by an automatic translation software. You can view the article source [:fr:Fonctionnalités d'Hosted Exchange 2010|here]. 

'''''What are the features of Hosted Exchange 2010 ?'''''

A description of the features of Hosted Exchange 2010 is available on the following link : [https://www.ikoula.com/portals/0/Ex10-fr-presentation.zip Ex10-en - presentation.zip]

We also transmit this document white label so you customize them to your corporate colours.

Contact our sales department to the 0890 710 712.

More info : [https://www.ex10.biz/fr/manager_ex10 Manager EX10]

[[Category:Hosted_Exchange]]
<comments />

Frequently asked questions about the cloud public ikoula

2015-09-29T09:02:50Z

Elocart87fda:

[[:fr:Questions fréquentes sur le cloud public ikoula]][[fr:Questions fréquentes sur le cloud public ikoula]]
 

This article has been created by an automatic translation software. You can view the article source [[:fr:Questions fréquentes sur le cloud public ikoula|here]]. 



5. Frequently asked questions on the cloud public ikoula

''Can I increase the memory and the number of processors ?''

Arrested instance : You can pass an offer of service to another in a quick way. This will allow you to modulate memory and processors.

It is also possible to act on the network throughput.

Started instance : It is possible to upgrade resources.

''Can we increase the size of volumes ?''

You can add new disks of data (DATADISK) to an instance. You can also resize a DATADISK However we recommend caution with this feature because he must not forget to anticipate the partitioning on the side of OS.

NB : Linux LVM is configured on our models.

NB 2 : It is not possible to resize a ROOTDISK.

''How the data is stored ? In the event of crash, how retrieve ?''

A started instance data are stored on the hypervisor.

Instance snapshots are stored on the hypervisor, it is possible from :

- Restore to a previous state.

Volume snapshots are stored on a storage network, their use allows :

- Once converted volume to be uploaded through the interface.

- To create a volume that can attach to an instance to proceed to data recovery.

- To restore to a previous state.

- Duplicate your instances by creating a template from a snapshot.

NB : Snapshots are not a backup solution, we recommend our solution instead of backup Idera.

NB 2 : You cannot take a snapshot of volume if you have a snapshot of the instance to which it is attached and vice versa.

''How many snapshots can be create ?''

Technically, you can do as much as you want.

If you have a Cloud private, you will be not limited.

Under a Cloud public, you are limited by default to 20.

''Can we set the hours of snapshotting via API ?''

It is possible to configure a recurring snapshot as well via the web interface via the API.

''How can I change the password for an instance ?''

When the instance is stopped, you can reset the password.

''Is there a system of « Data Recovery » ?''

We offer an outdoor solution to the Cloud public : "Idera», that allows to manage on an ongoing basis, the backup of the instance. It is also able to manage integrated database backup and restoration of the latter. The Data Recovery will be so in this way either (the product being opened, so you can use it with external solutions ), either with your own backup system (for example by doing a rsync your data ).

''Can you add IP addresses ?''

You can, in your router private, ask the acquisition of a new IP address that you will be charged if it is outside the contractual limitations.

''The interface is compatible with all browsers ? Use on mobile ?''

Yes, but we recommend a browser without any add - on or plugin. Some block features of the interface as the deployment for example Wizard.

It also works on mobile.

== One click ==
It is now possible from your interface extranet.ikoula.com to deploy a vm with a click and in less than thirty seconds, see rather :

{{#widget:YouTube|id=EZxaYj9s1Yk}}



 
This article seemed you to be useful ? <vote />





[[Category:[First_steps_on_cloud_public_ikoula]]
[[Category:Public_cloud]]
 
<comments />

Frequently asked questions about the cloud public ikoula

2015-09-29T09:02:37Z

Elocart87fda:

[[:fr:Questions fréquentes sur le cloud public ikoula]][[fr:Questions fréquentes sur le cloud public ikoula]]
 

This article has been created by an automatic translation software. You can view the article source [[:fr:Questions fréquentes sur le cloud public ikoula]]. 



5. Frequently asked questions on the cloud public ikoula

''Can I increase the memory and the number of processors ?''

Arrested instance : You can pass an offer of service to another in a quick way. This will allow you to modulate memory and processors.

It is also possible to act on the network throughput.

Started instance : It is possible to upgrade resources.

''Can we increase the size of volumes ?''

You can add new disks of data (DATADISK) to an instance. You can also resize a DATADISK However we recommend caution with this feature because he must not forget to anticipate the partitioning on the side of OS.

NB : Linux LVM is configured on our models.

NB 2 : It is not possible to resize a ROOTDISK.

''How the data is stored ? In the event of crash, how retrieve ?''

A started instance data are stored on the hypervisor.

Instance snapshots are stored on the hypervisor, it is possible from :

- Restore to a previous state.

Volume snapshots are stored on a storage network, their use allows :

- Once converted volume to be uploaded through the interface.

- To create a volume that can attach to an instance to proceed to data recovery.

- To restore to a previous state.

- Duplicate your instances by creating a template from a snapshot.

NB : Snapshots are not a backup solution, we recommend our solution instead of backup Idera.

NB 2 : You cannot take a snapshot of volume if you have a snapshot of the instance to which it is attached and vice versa.

''How many snapshots can be create ?''

Technically, you can do as much as you want.

If you have a Cloud private, you will be not limited.

Under a Cloud public, you are limited by default to 20.

''Can we set the hours of snapshotting via API ?''

It is possible to configure a recurring snapshot as well via the web interface via the API.

''How can I change the password for an instance ?''

When the instance is stopped, you can reset the password.

''Is there a system of « Data Recovery » ?''

We offer an outdoor solution to the Cloud public : "Idera», that allows to manage on an ongoing basis, the backup of the instance. It is also able to manage integrated database backup and restoration of the latter. The Data Recovery will be so in this way either (the product being opened, so you can use it with external solutions ), either with your own backup system (for example by doing a rsync your data ).

''Can you add IP addresses ?''

You can, in your router private, ask the acquisition of a new IP address that you will be charged if it is outside the contractual limitations.

''The interface is compatible with all browsers ? Use on mobile ?''

Yes, but we recommend a browser without any add - on or plugin. Some block features of the interface as the deployment for example Wizard.

It also works on mobile.

== One click ==
It is now possible from your interface extranet.ikoula.com to deploy a vm with a click and in less than thirty seconds, see rather :

{{#widget:YouTube|id=EZxaYj9s1Yk}}



 
This article seemed you to be useful ? <vote />





[[Category:[First_steps_on_cloud_public_ikoula]]
[[Category:Public_cloud]]
 
<comments />

Lack of space on the partition root for linux with plesk

2015-09-29T08:57:37Z

Elocart87fda:

[[:fr:Manque d'espace sur la partition root d'un linux avec plesk]][[fr:Manque d'espace sur la partition root d'un linux avec plesk]]
 

This article has been created by an automatic translation software. You can view the article source [[:fr:Manque d'espace sur la partition root d'un linux avec plesk|here]]. 




==Introduction== 
Vous manquez de place pour PLESK et souhaitez utiliser l'espace de la partition /data 
Par exemple, dans le cas d'un montage de ce type :


/dev/hda3 de 10 GO monté sur / 
/dev/hda4 de 40 GO monté sur /data

==Déroulé== 
Attention, il est fortement recommandé de faire un backup de votre serveur avant cette intervention.

Dans notre manipulation nous allons monter le /data, donc /dev/hda4, dans le /var, utilisé par plesk. Il faut donc stopper tous services utilisant des fichiers de /var (apache, mysql, plesk,... )

== Arrêt des services pouvant impacter le dossier /var == 
<syntaxhighlight lang="bash">
for i in {zabbix-agent,cron,bind9,dbus,atd,portmap,acpid,rsyslog,nfs-common,apache2}; do /etc/init.d/"$i" stop; done

/etc/init.d/psa stopall
</syntaxhighlight>
== Copie du contenu de /var /data == 
<syntaxhighlight lang="bash">
rsync -av /var/* /data
</syntaxhighlight>
le -av permet de garder les attributs des fichiers.

== Modification du fstab == 

En modifiant le fstab on va faire monter le /data dans le /var.
Nous avions indiqué dans la description du problème que /data correspondait à /dev/hda4
La ligne :
<syntaxhighlight lang="bash">
/dev/hda4 /data ext3 defaults 0 0
</syntaxhighlight>
devient donc
<syntaxhighlight lang="bash">
/dev/hda4 /var ext3 defaults 0 0
</syntaxhighlight>
Pour modifier le fstab vous pouvez utiliser cette commande :
<syntaxhighlight lang="bash">
vi /etc/fstab
</syntaxhighlight>

== Redémarrage du serveur == 


On utilise la commande "reboot"

== Libération de l'espace == 


Si votre site est fonctionnel à cette étape, vous pouvez définitivement libérer l'espace précédemment occupé en suivant ces étapes :
<syntaxhighlight lang="bash">
for i in {zabbix-agent,cron,bind9,dbus,atd,portmap,acpid,rsyslog,nfs-common,apache2}; do /etc/init.d/"$i" stop; done


/etc/init.d/psa stopall


umount /var
</syntaxhighlight>
/!\ à cette étape vérifiez que /var est bien démonté avant de lancer la commande suivante. si un processus bloque le démontage, vous le trouverez avec la commande /!\ <syntaxhighlight lang="bash"> lsof | grep "/var" </syntaxhighlight> 


libérer l'espace :
<syntaxhighlight lang="bash">
rm -rf /var/*


reboot
</syntaxhighlight>



 
Cet article vous a semblé utile ? <vote />


[[Category:Dedicated_server]]
[[Category:FLEX]]
[[Category:Linux]]
<comments />

How deploy a Docker container on an instance CoreOS Cloudstack by Ikoula

2015-09-25T09:00:08Z

Elocart87fda:

<span data-link_translate_fr_title="Comment deployer un container Docker sur une instance CoreOS Cloudstack by Ikoula" data-link_translate_fr_url="Comment_deployer_un_container_Docker_sur_une_instance_CoreOS_Cloudstack_by_Ikoula">[[:fr:Comment deployer un container Docker sur une instance CoreOS Cloudstack by Ikoula]][[fr:Comment deployer un container Docker sur une instance CoreOS Cloudstack by Ikoula]]

This article has been created by an automatic translation software. You can view the article source [[:fr:Comment deployer un container Docker sur une instance CoreOS Cloudstack by Ikoula|here]]. 


Docker is already integrated and ready to use on an instance deployed with our model "CoreOS stable" (Please refer to our article about this on our Blog at the link https://www.ikoula-blog.com/deploiement_instance_template_core-OS)


We assume that yor have followed our instructions for deploying an instance CoreOS and that yor are connected to it in SSH.


Check the current version of Docker (our CoreOS model is regularly updated so the version of Docker may change ) :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ docker version
Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.3.3
Git commit (client): a8a31ef-dirty
OS/Arch (client): linux/amd64
Server version: 1.5.0
Server API version: 1.17
Go version (server): go1.3.3
Git commit (server): a8a31ef-dirty
</syntaxhighlight>


We start by creating a local directory on our instance (in /home/core/) qui sera la racine de notre serveur web Nginx exécuté in notre container Docker.


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ pwd
/home/core
core@Coreosx64 ~ $ mkdir monsiteweb
</syntaxhighlight>


We place our web file (for our example we create a simple page type hello world ) :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ cd monsiteweb/
core@Coreosx64 ~/monsiteweb $ cat << EOF >> index.html
</syntaxhighlight>
<syntaxhighlight lang="html4strict">
<html>
<head>
<title>
Bienvenu sur la page de mon site hébergé sur un container docker Nginx Cloudstack by Ikoula.
</title>
</head>
<body>

Mon site hébergé sur un container docker Nginx sur mon instance CoreOS Cloudstack by Ikoula.

</body>
</html>
</syntaxhighlight>
<syntaxhighlight lang="bash">
EOF
</syntaxhighlight>


We can now start our container Docker Nginx exposing the contents of our local directory /home/core/monsiteweb sur le répertoire racine de Nginx in notre container :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ docker run --name monsiteweb -v /home/core/monsiteweb:/usr/share/nginx/html:ro -p 80:80 -p 443:443 -d nginx
Unable to find image 'nginx:latest' locally
Pulling repository nginx
fcf2ab262592: Download compland e
61b3964dfa70: Download compland e
f5224fc54ad2: Download compland e
a33ed00e1bc0: Download compland e
3e46ae27a4e2: Download compland e
6f42f0ded3bd: Download compland e
dc35357b56f1: Download compland e
1e0844d96b48: Download compland e
4663bae8c24d: Download compland e
c536168d418a: Download compland e
60b7b99e2a7e: Download compland e
a14a749327a7: Download compland e
Status: Downloaded newer image for nginx:latest
9c4b2daecea71415b2fedf317b78d77bf23e2c77182c25f8897be0a0dd66f241
</syntaxhighlight>


Our container Nginx "mywebsite " is running and listening on port 80 and 443 our instance CoreOS :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9c4b2daecea7 nginx:1 "nginx -g 'daemon of" About an hour ago Up About an hour 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp monsiteweb
</syntaxhighlight>


Il vous reste donc plus qu'à créer une règle de parefeu and de redirection de port pour autoriser les connexions sur les ports 80 and /or 443 and pouvoir accéder à votre site web :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ ip -o -f inet a sh dev eth0
2: eth0 inet 178.170.XX.XXX/24 brd 178.170.XX.XXX scope global eth0\ valid_lft forever preferred_lft forever
</syntaxhighlight>


Verification from a browser :


[[File: CloudStack_docker_nginx_ikoula.png]]


Cand article vous a semblé utile ? <vote />

[[category:cloudstack]]
[[category:public cloud]]
[[category:private cloud]]
[[category:Docker]]
[[category:CoreOS]]
<comments />

File:EX10 ConfOutl07mapi 0.gif

2015-09-25T07:57:01Z

Elocart87fda:

Category:API

2015-09-24T13:49:55Z

Elocart87fda: Created page with "API (acronym for Application Programming Interface) is a tool for developers. It allows technical interaction with Ikoula products (scripting, automation, personalized GUI ......"

API (acronym for Application Programming Interface) is a tool for developers. It allows technical interaction with Ikoula products (scripting, automation, personalized GUI ...) Currently in beta, all Ikoula products are not yet managed by the API.

How deploy a Docker container on an instance CoreOS Cloudstack by Ikoula

2015-09-24T09:22:42Z

Elocart87fda:

<span data-link_translate_fr_title="Comment deployer un container Docker sur une instance CoreOS Cloudstack by Ikoula" data-link_translate_fr_url="Comment_deployer_un_container_Docker_sur_une_instance_CoreOS_Cloudstack_by_Ikoula">[[:fr:Comment deployer un container Docker sur une instance CoreOS Cloudstack by Ikoula]][[fr:Comment deployer un container Docker sur une instance CoreOS Cloudstack by Ikoula]]

This article has been created by an automatic translation software. You can view the article source [[:fr:Comment deployer un container Docker sur une instance CoreOS Cloudstack by Ikoula|here]]. 


Docker is already integrated and ready to use on an instance deployed with our model "CoreOS stable" (Please refer to our article about this on our Blog at the link https://www.ikoula-blog.com/deploiement_instance_template_core-OS)


We assume that yor have followed our instructions for deploying an instance CoreOS and that yor are connected to it in SSH.


Check the current version of Docker (our CoreOS model is regularly updated so the version of Docker may change ) :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ docker version
Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.3.3
Git commit (client): a8a31ef-dirty
OS/Arch (client): linux/amd64
Server version: 1.5.0
Server API version: 1.17
Go version (server): go1.3.3
Git commit (server): a8a31ef-dirty
</syntaxhighlight>


We start by creating a local directory on our instance (in /home/core/) qui sera la racine de notre serveur web Nginx exécuté in notre container Docker.


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ pwd
/home/core
core@Coreosx64 ~ $ mkdir monsiteweb
</syntaxhighlight>


We place our web file (for our example we create a simple page type hello world ) :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ cd monsiteweb/
core@Coreosx64 ~/monsiteweb $ cat << EOF >> index.html
</syntaxhighlight>
<syntaxhighlight lang="html4strict">
<html>
<head>
<title>
Bienvenu sur la page de mon site hébergé sur un container docker Nginx Cloudstack by Ikoula.
</title>
</head>
<body>

Mon site hébergé sur un container docker Nginx sur mon instance CoreOS Cloudstack by Ikoula.

</body>
</html>
</syntaxhighlight>
<syntaxhighlight lang="bash">
EOF
</syntaxhighlight>


We can now start our container Docker Nginx exposing the contents of our local directory /home/core/monsiteweb sur le répertoire racine de Nginx in notre container :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ docker run --name monsiteweb -v /home/core/monsiteweb:/usr/share/nginx/html:ro -p 80:80 -p 443:443 -d nginx
Unable to find image 'nginx:latest' locally
Pulling repository nginx
fcf2ab262592: Download compland e
61b3964dfa70: Download compland e
f5224fc54ad2: Download compland e
a33ed00e1bc0: Download compland e
3e46ae27a4e2: Download compland e
6f42f0ded3bd: Download compland e
dc35357b56f1: Download compland e
1e0844d96b48: Download compland e
4663bae8c24d: Download compland e
c536168d418a: Download compland e
60b7b99e2a7e: Download compland e
a14a749327a7: Download compland e
Status: Downloaded newer image for nginx:latest
9c4b2daecea71415b2fedf317b78d77bf23e2c77182c25f8897be0a0dd66f241
</syntaxhighlight>


Our container Nginx "mywebsite " is running and listening on port 80 and 443 our instance CoreOS :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9c4b2daecea7 nginx:1 "nginx -g 'daemon of" About an hour ago Up About an hour 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp monsiteweb
</syntaxhighlight>


Il vous reste donc plus qu'à créer une règle de parefeu and de redirection de port pour autoriser les connexions sur les ports 80 and /or 443 and pouvoir accéder à votre site web :


<syntaxhighlight lang="bash">
core@Coreosx64 ~ $ ip -o -f inet a sh dev eth0
2: eth0 inet 178.170.XX.XXX/24 brd 178.170.XX.XXX scope global eth0\ valid_lft forever preferred_lft forever
</syntaxhighlight>


Verification from a browser :


[[File: CloudStack_docker_nginx_ikoula.png]]


Cand article vous a semblé utile ? <vote />

[[category:cloudstack]]
[[category:cloud public]]
[[category:cloud priv��]]
[[category:Docker]]
[[category:CoreOS]]
<comments />

First steps on the Cloud Public Ikoula

2015-09-23T08:00:50Z

Elocart87fda:

[[:fr:Premiers pas sur le Cloud Public Ikoula]][[fr:Premiers pas sur le Cloud Public Ikoula]] 

This article has been created by an automatic translation software. You can view the article source [[:fr:Premiers pas sur le Cloud Public Ikoula|here]]. 



Table of contents

1. [[Ikoula cloud areas]]

a. "area | | Advance-Routing |!| b. "area | |

|!| a. deployment Direct-Routing |!| b. "area | |

2. [[Deploiement d'une instance en zone direct-routing]]

c. how to allow an SSH connection to your machine

virtual in a security group

d. create rules to allow connections between virtual machines in a security group examples (Direct-Routing).

e. how to configure rules Firewall of traffic entering a security group (Direct-Routing)f. how to configure rules Firewall's outbound in a security group

Examples of network configuration for the instances (Direct-Routing).

Accessibility outside for an instance type GNU SSH (Direct-Routing).

3. [[Deploiement d'une instance en zone advanced-routing]]

- RDP from outside for a type instance

- Accessibility TS /RDP from outside for a type instance

- a. generate its API keys /b. for calls to the API basics MS Windows.

4. [[Utiliser le moteur API du cloud public ikoula]]

For more information on the platform

If you have any questions, do not hesitate to contact

5. [[Questions fréquentes sur le cloud public ikoula]]

6. [[Lexique Cloudpublic]]

7. [[Questions fréquentes sur le cloud public ikoula#One click|Déployez vos vm en un seul clic et en moins de trente secondes]]

This article seemed you to be useful :

[https://express.ikoula.com/fr/cloud-public Page cloud public ikoula]

[https://www.youtube.com/playlist?list=PLKK_ECuHPQqAdOJ8uy0X9DGosLKreBcKS&feature=view_all See our demos videos]

[https://www.ikoula-blog.com/taxonomy/term/323 See our blog articles]

:

- [mailto:ikoula@ikoula.com Notre support technique]

- [mailto:sales@ikoula.com Notre service commercial]



 
? <vote />





[[Category:[First_steps_on_cloud_public_ikoula]]
[[Category:Public_cloud]]
<comments />

File:Lync skype 1.jpg

2015-09-23T07:30:10Z

Elocart87fda: