Alliance Doc

Translations:Cloud Quick Start/16/fr: Difference between revisions

Translation unit Discussion

Translations:Cloud Quick Start/16/fr (view source)

Revision as of 22:07, 6 July 2020

73 bytes added ,  4 years ago
no edit summary
No edit summary
No edit summary
Line 2: Line 2:
*Faites afficher la page des instances avec ''Compute->Instances''.
*Faites afficher la page des instances avec ''Compute->Instances''.
*Un menu déroulant se trouve à la fin de la ligne de votre instance; cliquez sur l'icône ▼ et sélectionnez  ''Associer une adresse IP flottante''.
*Un menu déroulant se trouve à la fin de la ligne de votre instance; cliquez sur l'icône ▼ et sélectionnez  ''Associer une adresse IP flottante''.
*If this is your first time associating a floating IP, you need to click on the “+” sign in the ''IP Address'' dialog box. If you need to allocate a public IP address for this VM again in the future you can select one from the list by clicking the ▼ in the '''IP Address''' dialogue box.
*Si vous faites cette association pour la première fois, cliquez sur l'icône + du champ ''Adresse IP''. If you need to allocate a public IP address for this VM again in the future you can select one from the list by clicking the ▼ in the '''IP Address''' dialogue box.
#*Click on the ''Associate'' button.
#*Click on the ''Associate'' button.
#*You should now have two IP address in your IP address column. One will be of the form <code>192.168.X.Y</code>, the other one is your public IP. You can also find a list of your public IP addresses and their associated projects by going to '''Network->Floating IPs. You will need your public IP when you are trying to connect to your VM.'''
#*You should now have two IP address in your IP address column. One will be of the form <code>192.168.X.Y</code>, the other one is your public IP. You can also find a list of your public IP addresses and their associated projects by going to '''Network->Floating IPs. You will need your public IP when you are trying to connect to your VM.'''
#''Configure Firewall''
'''Configurer le coupe-feu'''
#*Using the left navigation pane go to '''Network->Security Groups'''.
#*Using the left navigation pane go to '''Network->Security Groups'''.
#*On the group row named '''default''', click the [[File:Manage-Rules-Button.png]] on the far right.
#*On the group row named '''default''', click the [[File:Manage-Rules-Button.png]] on the far right.
Line 13: Line 13:
#*In the '''CIDR''' dialogue box replace the <code>0.0.0.0/0</code> in the CIDR text box with <code>your-ip/32</code>. Note that this is the IP address of the physical computer you are wanting to use to connect to your VM. If you don't know your current IP address you can see it by going to [http://ipv4.icanhazip.com ipv4.icanhazip.com] in your browser. If you want to access your VM from other IPs you can add more rules with different IP addresses. If you want to specify a range of IP addresses use [https://www.ipaddressguide.com/cidr this tool] to calculate your CIDR rule for a range of IP addresses.
#*In the '''CIDR''' dialogue box replace the <code>0.0.0.0/0</code> in the CIDR text box with <code>your-ip/32</code>. Note that this is the IP address of the physical computer you are wanting to use to connect to your VM. If you don't know your current IP address you can see it by going to [http://ipv4.icanhazip.com ipv4.icanhazip.com] in your browser. If you want to access your VM from other IPs you can add more rules with different IP addresses. If you want to specify a range of IP addresses use [https://www.ipaddressguide.com/cidr this tool] to calculate your CIDR rule for a range of IP addresses.
#*Finally, click the ''Add'' button. Now the rule you just created should show up on the list in security groups.
#*Finally, click the ''Add'' button. Now the rule you just created should show up on the list in security groups.
#Important Notes
'''Points importants'''
#*'''Do not remove the default security rules''' as this will affect the ability of your VM to function properly (see [[OpenStack#Security_Groups|security groups]]).
*'''Ne supprimez pas les règles de sécurité par défaut'''; le fonctionnement de votre instance  serait compromis (voir [[OpenStack/fr#Groupes_de_sécurité|Groupes de sécurité]]).
#*'''Security rules cannot be edited''', they can only be deleted and re-added.So if you make a mistake when creating a security group rule you need to delete it using the '''Delete This''' button on the far left of the row for that rule in the security groups screen, and then re-add it correctly from scratch using the '''Add Rule''' button.
*'''Ne modifiez pas les règles de sécurité''', they can only be deleted and re-added.So if you make a mistake when creating a security group rule you need to delete it using the '''Delete This''' button on the far left of the row for that rule in the security groups screen, and then re-add it correctly from scratch using the '''Add Rule''' button.
#*If you change your network location (and therefore your IP address) then you need to add the security rule described in this section for that new IP address. Remember that when you change your physical location (example working on-campus vs working from home) you are changing your network location.
*Si vous changez l'endroit de votre r (and therefore your IP address) then you need to add the security rule described in this section for that new IP address. Remember that when you change your physical location (example working on-campus vs working from home) you are changing your network location.
#*If you do not have a static IP address for the network you are using remember that it can sometimes change, so if you can no longer connect to your VM after a period of time sometimes it's worth checking to see if your IP address has changed. You can do this by putting [http://ipv4.icanhazip.com ipv4.icanhazip.com] in your browser and seeing if it matches what you have in your security rule. If your IP address changes frequently, but the left-most numbers always stay the same, it could make more sense to add a range of IP addresses rather than frequently modifying your security rules. Use [https://www.ipaddressguide.com/cidr this tool] for determining a CIDR IP range from an IP range or learn more about CIDR notation [https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation here].
*If you do not have a static IP address for the network you are using remember that it can sometimes change, so if you can no longer connect to your VM after a period of time sometimes it's worth checking to see if your IP address has changed. You can do this by putting [http://ipv4.icanhazip.com ipv4.icanhazip.com] in your browser and seeing if it matches what you have in your security rule. If your IP address changes frequently, but the left-most numbers always stay the same, it could make more sense to add a range of IP addresses rather than frequently modifying your security rules. Use [https://www.ipaddressguide.com/cidr this tool] for determining a CIDR IP range from an IP range or learn more about CIDR notation [https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation here].
#*It can be helpful to add a description about what a security rule is for, e.g. home or office. That way you will know which rule is no longer needed if you need to add a new rule while connecting, for example, from home.
*Il pourrait être utile de fournir une description pour une règle de sécurité, par exemple ''bureau'' ou ''maison''. Vous pourrez ainsi savoir si une règle n'est plus nécessaire quand vous voulez ajouter une nouvelle règle pour vous connecter par exemple de la maison.
Diane27
rsnt_translations
56,430

edits

Retrieved from "https://docs.alliancecan.ca/wiki/Special:MobileDiff/85970"