STEP 1:-<\/strong><\/p>\n\n\n\n Created an instance of having Centos 7.9 <\/strong>https:\/\/aws.amazon.com\/marketplace\/pp\/prodview-foff247vr2zfw?sr=0-1&ref_=beagle&applicationId=AWSMPContessa<\/a><\/p>\n\n\n\n Then we provide directories and partitions as follows,<\/p>\n\n\n\n On the AWS console, get the volume added for the 3 more directories along with the root directory which is 4 together, as [8+1+1+1] initial setup.<\/p>\n\n\n\n xvdf,xvdg,xvdh<\/strong> as follows we will be created for the 3 directories<\/p>\n\n\n\n Now after initiating the basic setup of, a formal VM from centos 7.9 , 4 disk spaces.<\/strong><\/p>\n\n\n\n ————————————————————————————————————-<\/p>\n\n\n\n STEP 2:-<\/strong><\/p>\n\n\n\n (update the system provide the partition and mount the disk to each of the directories)<\/p>\n\n\n\n sudo yum update<\/strong><\/p>\n\n\n\n [The fdisk<\/strong> command in Linux is used to create and manipulate disk partition tables]<\/p>\n\n\n\n fdisk -d Delete a partition<\/p>\n\n\n\n fdisk -m Print the available (FDISK) commands<\/p>\n\n\n\n fdisk -n Add a new partition<\/p>\n\n\n\n fdisk -p Print the partition table<\/p>\n\n\n\n fdisk -w Write the table to the hard drive<\/p>\n\n\n\n Now, create the partition of new and default primary partition to each of the directories.<\/p>\n\n\n\n The mount has to happen with three of the directories, one to maintain for the root which is home dir, another one is for Synopsys tools to be implemented and on the other hand to have data stored for the future addition task added.<\/p>\n\n\n\n this follows the below format,once attached it to the instance<\/p>\n\n\n\n partition -> formatting -> mounting to the mount point.<\/p>\n\n\n\n sudo fdisk \/dev\/xvdf<\/strong><\/p>\n\n\n\n sudo mkfs.xfs \/dev\/xvdf1<\/strong><\/p>\n\n\n\n sudo mkdir -p \/ve\/home<\/strong><\/p>\n\n\n\n sudo mount \/dev\/xvdf1 \/ve\/home<\/strong><\/p>\n\n\n\n sudo fdisk \/dev\/xvdg<\/strong><\/p>\n\n\n\n sudo mkfs.xfs \/dev\/xvdg1<\/strong><\/p>\n\n\n\n sudo mkdir \/usr\/synopsys<\/strong><\/p>\n\n\n\n sudo mount \/dev\/xvdg1 \/usr\/synopsys<\/strong><\/p>\n\n\n\n sudo fdisk \/dev\/xvdh<\/strong><\/p>\n\n\n\n sudo mkfs.xfs \/dev\/xvdh1<\/strong><\/p>\n\n\n\n sudo mkdir \/data<\/strong><\/p>\n\n\n\n The above commands will fill and mount the disk partition.<\/p>\n\n\n\n Now reboot<\/strong> the system.<\/p>\n\n\n\n ———————————————————————————————————————<\/p>\n\n\n\n –Now mount the storage volume with use of fstab<\/p>\n\n\n\n [Note: edit with care when working with fstab file]<\/p>\n\n\n\n vi fstab [automatically mount the storage volume when we start the Linux machine].<\/p>\n\n\n\n get inside the etc\/fstab to add information about the disk,<\/p>\n\n\n\n sudo vi \/etc\/fstab<\/strong><\/p>\n\n\n\n you’ll get the UUID<\/strong> of each ——————————————————————————————————————————————<\/p>\n\n\n\n We now created a new storage volume by modifying the existing volume of the \/usr\/synopsys for 50GB<\/strong>.<\/p>\n\n\n\n Ec2->volume-> select the volume storage-> enter the modify option->change it to 50GB.<\/p>\n\n\n\n Now to attach the modified volume give the commands below,<\/p>\n\n\n\n sudo growpart \/dev\/xvdg 1<\/strong><\/p>\n\n\n\n and extend the volume to the particular disk as given below to its directory<\/p>\n\n\n\n sudo xfs_growfs -d \/usr\/synopsys<\/strong><\/p>\n\n\n\n now we need to add a user to give access to the whole machine for that we need to provide the user and SSH login authentication way, give the autherized_key to the server machine in its SSH directory.<\/p>\n\n\n\n creating user,<\/p>\n\n\n\n and create a directory for this user to store their key<\/p>\n\n\n\n now edit and add the authorized_keys inside it,<\/p>\n\n\n\n get the key from the root we already had,<\/p>\n\n\n\n recursively change the owner permission to the below user,<\/p>\n\n\n\n also centos,<\/p>\n\n\n\n The By running the above command, you are setting the permissions for the changes all the users and makes the group of users that you want to add the superuser.<\/p>\n\n\n\n “Now with this, we can able to login to the server machine using the user that we added here”.<\/p>\n\n\n\n use the above image to launch the instance.<\/p>\n\n\n\n with the use of an AWS S3 bucket where we store all our required software packages to be installed to work with the Synopsys tools, hence we need to configure AWS to use s3.<\/p>\n\n\n\n at some point .\/aws\/install might not work so apply it separately to the terminal<\/p>\n\n\n\n to check if the aws cli is installed check with,<\/p>\n\n\n\n now integrate<\/strong> with the IAM user of our AWS ACCOUNT<\/strong> where we have our package installed.<\/p>\n\n\n\n Enter the given inputs on the sections, so that we get inside our account and the permissions we are allowed to take charge of,<\/p>\n\n\n\n now get all the software packages from the s3 bucket <\/strong>we’ve,<\/p>\n\n\n\n now to install binaries<\/p>\n\n\n\n mkdir wa<\/strong><\/p>\n\n\n\n cd wa<\/strong><\/p>\n\n\n\n The Once you’ve executed this command, the environment variable make the entries for bashrc<\/strong> file<\/p>\n\n\n\n in this file give these entries at the last line of the file.<\/p>\n\n\n\n now with the help of two scripts, we are going to initiate and launch the Synopsys tools.<\/p>\n\n\n\n change the execution permission,<\/p>\n\n\n\n initializing the setup of synopsys installer.<\/p>\n\n\n\n![\"\"](\"https:\/\/swstech.sws-international.com\/wordpress\/wp-content\/uploads\/2023\/12\/image-1024x457.png\")
<\/figure>\n\n\n\n<\/figure>\n\n\n\n![\"\"](\"https:\/\/swstech.sws-international.com\/wordpress\/wp-content\/uploads\/2023\/12\/image-1.png\")
<\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\nUUID=\"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx\"<\/code>: This is the Universally Unique Identifier associated with the device or partition. UUIDs are used to uniquely identify storage devices, and they are often used in configuration files and scripts to mount the devices.<\/p>\n\n\n\nUUID=xxxxxxx-3769-4ad9-8460-xxxxxxxxxx \/ xfs defaults 0 0\nUUID=xxxxxxx-c139-4ea0-97bb-xxxxxxxxxxxx\/usr\/synopsys\tauto\tdefaults,nofail,comment=cloudconfig\t0\t0\nUUID=xxxxxxxx-6ea5-4987-be0f-xxxxxxxxx \/ve\/home xfs defaults,nofail,rw,seclabel,relatime,attr2,inode64,usrquota,prjquota,grpquota 0 0\nthis above file indicates the set of par<\/code><\/pre>\n\n\n\n
\n\n\n\nsudo useradd khelender<\/code><\/p>\n\n\n\nsudo mkdir \/home\/khelender\/.ssh<\/code><\/p>\n\n\n\nsudo vi \/home\/khelender\/.ssh\/authorized_keys<\/code><\/p>\n\n\n\nsudo vi \/root\/.ssh\/authorized_keys<\/code><\/p>\n\n\n\nsudo chown -R khelender ~\/.ssh\/<\/code><\/p>\n\n\n\nsudo chown -R centos:centos ~\/.ssh\/<\/code><\/p>\n\n\n\nsudo chown -R khelender:khelender ~khelender\/.ssh<\/code><\/p>\n\n\n\nsudo chown -R khelender:khelender ~khelender\/.ssh<\/code> command is used to change the ownership of the .ssh<\/code> directory and its contents to the user “khelender” and the group “khelender.”<\/p>\n\n\n\nsudo chmod 600 ~khelender\/.ssh\/authorized_keys<\/code><\/p>\n\n\n\nauthorized_keys<\/code> file to allow only the owner, in this case, the user “khelender,” to read and write to the file.<\/p>\n\n\n\nsudo vi \/etc\/sudoers<\/code><\/p>\n\n\n\n\/etc\/sudoers<\/code>: This is the path to the sudoers file. It’s the main configuration file for the sudo<\/code> command, where you define who can run which commands with elevated privileges.<\/p>\n\n\n\nsudo vi \/etc\/group<\/code><\/p>\n\n\n\nwe’ve our AMI available which has all the specs pre-built for the above steps.<\/h1>\n\n\n\n
![\"\"\/](\"https:\/\/cdn.hashnode.com\/res\/hashnode\/image\/upload\/v1699350832991\/0776b845-f57d-4ab8-b606-6e3086c02180.png\")
<\/figure>\n\n\n\n
\n\n\n\nInstall the Synopsys tools by configuring AWS<\/h1>\n\n\n\n
curl \"<\/code>https:\/\/awscli.amazonaws.com\/awscli-exe-linux-x86_64.zip<\/code><\/a>\" -o \"<\/code>awscliv2.zip<\/code><\/a>\" && unzip<\/code> awscliv2.zip<\/code><\/a> && .\/aws\/install<\/code><\/p>\n\n\n\n.\/aws\/install<\/code><\/p>\n\n\n\naws --version<\/code><\/p>\n\n\n\naws configure<\/code><\/p>\n\n\n\nAWS Access Key ID [****************ABCD]:\nAWS Secret Access Key [****************efgh]:\nDefault region name [us-east-1]:\nDefault output format [json]:<\/code><\/pre>\n\n\n\naws s3 --profile ${profile} ls s3:\/\/ve-setup-binaries<\/code><\/p>\n\n\n\nexport profile=default<\/code> command sets an environment variable named profile<\/code> with the value “default.” In many programming and scripting languages, including shell scripting, you can use the export<\/code> command to create or modify environment variables.<\/p>\n\n\n\nprofile<\/code> will be available for use in your shell session or any scripts that you run within that session. You can access the value of the profile<\/code> variable using the $profile<\/code> syntax<\/p>\n\n\n\n
\n\n\n\nsudo vi \/etc\/bashrc<\/code><\/p>\n\n\n\n![\"\"\/](\"https:\/\/cdn.hashnode.com\/res\/hashnode\/image\/upload\/v1699367878615\/b3c5d484-6cdf-4f2e-a4c2-44ad67594150.png\")
<\/figure>\n\n\n\nexport SNPSLMD_LICENSE_FILE=xxxxx@xxx-yyyyyyyyyy.com\nexport PATH=$PATH:\/usr\/synopsys\/icc2\/S-2021.06-SP5\/bin:\/usr\/synopsys\/wv\/S-2021.09-SP2-2\/bin:\/usr\/synopsys\/prime\/S-2021.06-SP5\/bin<\/code><\/pre>\n\n\n\n![\"\"\/](\"https:\/\/cdn.hashnode.com\/res\/hashnode\/image\/upload\/v1699367969611\/ca9a378c-74d7-4e7a-88a3-bf263f6bf613.png\")
<\/figure>\n\n\n\n
\n\n\n\nsudo vi setup_installer.sh<\/code><\/p>\n\n\n\nchmod +x setup_installer.sh<\/code><\/p>\n\n\n\nsetup_installer.sh<\/h3>\n\n\n\n
#!\/bin\/bash\n# ---------------------------------------------------------\n# setup_installer.sh : setup synopsys installer\n# ---------------------------------------------------------\nfunction setup_env() {\n logfile=\/tmp\/remote_tool_install.log\n profile=default\n echo \" ------------ Installer install Run @ `date` --------- \" >> $logfile\n set +x\n # -------- Checkup existence of profile ------------\n aws s3 --profile ${profile} ls s3:\/\/ve-setup-binaries\/ > \/dev\/null 2>&1 \n status=$?\n if [[ $status -ne 0 ]] ; then\n\techo \"ERROR: profile ${profile} not available! exiting.\"\n\texit 1\n fi\n}\n\nfunction setup_installer() {\n # -------- Setup installer ------------\n if [[ ! -f \/usr\/synopsys\/installer\/installer ]]\n then\n \t# echo \"------Installer binary available, installing it------\" ; return ;\n\taws s3 --profile ${profile} sync s3:\/\/ve-setup-binaries\/installer installer >> $logfile\n\techo \/usr\/synopsys\/installer | perl installer\/SynopsysInstaller_v5.4.run \n\n\tsudo chown -R centos:centos \/usr\/synopsys\n\techo \"Synopsys Installer has been setup at \/usr\/synopsys \"\n else\n \techo \"------- Installer already available in \/usr\/synopsys\/installer\/installer !\"\n\treturn\n fi\n}\n\necho \"Installing Synopsys installer at \/usr\/synopsys\/installer\/installer\"\nsetup_env\nsetup_installer<\/code><\/pre>\n\n\n\n![\"\"\/](\"https:\/\/cdn.hashnode.com\/res\/hashnode\/image\/upload\/v1699358489945\/d573f72c-5b36-4cb3-8718-38084ead6324.png\")
<\/figure>\n\n\n\nsudo vi install_tools.sh<\/code><\/p>\n\n\n\ninstall_tools.sh<\/h3>\n\n\n\n
#!\/bin\/bash\n# ---------------------------------------------------------\n# install_tools.sh: setup tools\n# ---------------------------------------------------------\nfunction setup_env() {\n logfile=\/tmp\/remote_tool_install.log\n profile=default\n echo \" ------------ Tool install Run @ `date` --------- \" >> $logfile\n set +x\n # -------- Checkup existence of profile ------------\n aws s3 --profile ${profile} ls s3:\/\/ve-setup-binaries\/ > \/dev\/null 2>&1 \n status=$?\n if [[ $status -ne 0 ]] ; then\n\techo \"ERROR: profile ${profile} not available! exiting.\"\n\texit 1\n fi\n}\n\nfunction setup_tools() {\n # -------- Setup tools ------------\n tools=\"$@\"\n #tools=\"icc2 dc prime formality hspice wv\" # customcompiler starrc\"\n echo \"Setting up tools $tools\"\n for tool in $tools\n do\n\techo \"========================= Setting up tool $tool =================\"\n\tfolder=$tool\n\tif [[ ($tool == \"dc\") ]] ; then\n\t folder=syn\n\telif [[ ($tool == \"formality\") ]] ; then\n\t folder=fm\n\tfi\n\n\t# ----- Check existence of tool installer on s3 bucket\n\taws s3 --profile ${profile} ls s3:\/\/ve-setup-binaries\/$tool > \/dev\/null 2>&1 \n\tstatus=$?\n\tif [[ $status -ne 0 ]] ; then\n\t echo \"ERROR: Tool $tool not available in s3 bucket\"\n\t continue\n\tfi\n\n\techo \"------- Installing tool $tool in folder $folder --------\"\n\tif [[ ! -d \/usr\/synopsys\/$folder ]] ; then\n\t echo \"Setting up tool $tool\"\n\t aws s3 --profile ${profile} sync s3:\/\/ve-setup-binaries\/$tool $tool >> $logfile\n\t input=\"yes\\nyes\\n\"\n\t echo -e $input | \/usr\/synopsys\/installer\/installer -source $tool -target \/usr\/synopsys -site_info site_info.txt\n\telse\n\t echo \"WARNING! Folder $folder for tool $tool already exists! skipping.\"\n\tfi\n done\n rm -rf snps*temp*\n}\n\nif [[ $# -gt 0 ]] ; then\n setup_env\n setup_tools \"$@\"\nelse\n echo \"ERROR: NO args given. Format:'$0 <tool1> [<tool2> ....]'\"\nfi<\/code><\/pre>\n\n\n\n
![\"\"\/](\"https:\/\/cdn.hashnode.com\/res\/hashnode\/image\/upload\/v1699365818073\/2d488cef-6dc7-45eb-9a08-b91ae89048f8.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/cdn.hashnode.com\/res\/hashnode\/image\/upload\/v1699367007525\/5ee0da54-82dc-47f8-a507-67e02b8cb16b.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/cdn.hashnode.com\/res\/hashnode\/image\/upload\/v1699368301581\/4c697464-3963-42a0-94c4-0b9ca3c9b285.png\")
<\/figure>\n\n\n\n