Coder Social home page Coder Social logo

faas's People

Contributors

factorable avatar gchilders avatar jabbany avatar joshdabosh avatar lukevalenta avatar shaananc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

faas's Issues

Public IP Attribute Error when running build-base.sh

[root@ip-172-31-33-196 ec2]# ./build-base.sh
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to allow bad characters in group names by default, this will change, but still be user
configurable on deprecation. This feature will be removed in version 2.10. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details

PLAY [Launch EC2 instance] ***********************************************************************************************************************************************

TASK [Gathering Facts] ***************************************************************************************************************************************************
ok: [localhost]

TASK [launch : Launch EC2 instance(s)] ***********************************************************************************************************************************
changed: [localhost]

TASK [launch : Add new instance to host group] ***************************************************************************************************************************
fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'public_ip'\n\nThe error appears to be in '/opt/faas/ec2/roles/launch/tasks/main.yml': line 32, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n # Add to host group so we can see this node later in the playbook.\n- name: Add new instance to host group\n ^ here\n"}

NO MORE HOSTS LEFT *******************************************************************************************************************************************************

PLAY RECAP ***************************************************************************************************************************************************************
localhost : ok=2 changed=1 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0

Can this factor 768 bit integers?

Can a modification to this repository factor 768 bit integers? If not do you know of another repository or tool that can handle 768? My understanding is that 768 bit has been broken for at least a decade but I can't find any tools to factor it.

msieve version mismatch

In ec2/roles/build/tasks/install-msieve.yml, it is

get_url: dest={{ sourcedir }}/msieve.tar.gz url='https://sourceforge.net/projects/msieve/files/latest/download?source=files'

It fails now because the latest version of msieve on sourceforge has been 1.5.3. And the commands below hard code directory msieve-1.5.2. It can be

get_url: dest={{ sourcedir }}/msieve.tar.gz url='https://sourceforge.net/projects/msieve/files/msieve/Msieve%20v1.52/msieve152.tar.gz' checksum="sha1:88a1ce2354b57835231bcaca0ecb0477b975b5cd"

to avoid the problem simply. If anyone want to upgrade the msieve to the latest version, maybe the patch file should be changed. I haven't tested it.

Anyway, I think the project is helpful and it do help me to factor a integer. ๐Ÿ‘

Error when launching

I get this error every time I run ./test-factor.sh. I believe it is to do with the line instance_id: โ€œ{{ hostvars[groups[ami_builder.group][0]].ec2_id }}โ€ in build-finish.yml. Any help would be much appreciated.

./test-factor.sh
 [WARNING]: provided hosts list is empty, only localhost is available


PLAY [Launch EC2 instance] *****************************************************

TASK [setup] *******************************************************************
ok: [localhost]

TASK [launch : Launch EC2 instance(s)] *****************************************
changed: [localhost]

TASK [launch : Add new instance to host group] *********************************
changed: [localhost] => (item={u'kernel': None, u'root_device_type': u'ebs', u'private_dns_name': u'ip-10-0-0-8.us-west-2.compute.internal', u'public_ip': u'35.165.135.112', u'private_ip': u'10.0.0.8', u'id': u'i-091291f85e94c9a99', u'ebs_optimized': False, u'state': u'running', u'virtualization_type': u'hvm', u'root_device_name': u'/dev/sda1', u'ramdisk': None, u'block_device_mapping': {u'/dev/sda1': {u'status': u'attached', u'delete_on_termination': True, u'volume_id': u'vol-0ecb64135cfe3dd39'}}, u'key_name': u'faas', u'image_id': u'ami-5189a661', u'tenancy': u'default', u'groups': {u'sg-2ddb4255': u'faas'}, u'public_dns_name': u'ec2-35-165-135-112.us-west-2.compute.amazonaws.com', u'state_code': 16, u'tags': {u'launch_group': u'faas_ami_builder', u'Name': u'faas_ami_builder'}, u'placement': u'us-west-2a', u'ami_launch_index': u'0', u'dns_name': u'ec2-35-165-135-112.us-west-2.compute.amazonaws.com', u'region': u'us-west-2', u'launch_time': u'2017-02-07T00:56:01.000Z', u'instance_type': u'm4.large', u'architecture': u'x86_64', u'hypervisor': u'xen'})

TASK [launch : Wait for SSH to come up] ****************************************
ok: [localhost] => (item={u'kernel': None, u'root_device_type': u'ebs', u'private_dns_name': u'ip-10-0-0-8.us-west-2.compute.internal', u'public_ip': u'35.165.135.112', u'private_ip': u'10.0.0.8', u'id': u'i-091291f85e94c9a99', u'ebs_optimized': False, u'state': u'running', u'virtualization_type': u'hvm', u'root_device_name': u'/dev/sda1', u'ramdisk': None, u'block_device_mapping': {u'/dev/sda1': {u'status': u'attached', u'delete_on_termination': True, u'volume_id': u'vol-0ecb64135cfe3dd39'}}, u'key_name': u'faas', u'image_id': u'ami-5189a661', u'tenancy': u'default', u'groups': {u'sg-2ddb4255': u'faas'}, u'public_dns_name': u'ec2-35-165-135-112.us-west-2.compute.amazonaws.com', u'state_code': 16, u'tags': {u'launch_group': u'faas_ami_builder', u'Name': u'faas_ami_builder'}, u'placement': u'us-west-2a', u'ami_launch_index': u'0', u'dns_name': u'ec2-35-165-135-112.us-west-2.compute.amazonaws.com', u'region': u'us-west-2', u'launch_time': u'2017-02-07T00:56:01.000Z', u'instance_type': u'm4.large', u'architecture': u'x86_64', u'hypervisor': u'xen'})

PLAY RECAP *********************************************************************
localhost                  : ok=4    changed=2    unreachable=0    failed=0   

 [WARNING]: provided hosts list is empty, only localhost is available

[DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and 
make sure become_method is 'sudo' (default).
This feature will be removed in a 
future release. Deprecation warnings can be disabled by setting 
deprecation_warnings=False in ansible.cfg.

PLAY RECAP *********************************************************************

 [WARNING]: provided hosts list is empty, only localhost is available


PLAY [Create AMI from running instance and terminate instance upon completion] *

TASK [setup] *******************************************************************
ok: [localhost]

TASK [Remove previous custom image (if it exists)] *****************************
ok: [localhost]

TASK [Create AMI from temporary instance] **************************************
fatal: [localhost]: FAILED! => {"failed": true, "msg": "the field 'args' has an invalid value, which appears to include a variable that is undefined. The error was: 'dict object' has no attribute u'tag_Name_faas_ami_builder'\n\nThe error appears to have been in '/Users/usr/faas/ec2/build-finish.yml': line 17, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n    - name: Create AMI from temporary instance\n      ^ here\n"}
	to retry, use: --limit @/Users/usr/faas/ec2/build-finish.retry

PLAY RECAP *********************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=1   

MaxSpotInstanceCountExceeded

Howdy. I was able to run ./test-factor.sh and successfully cracked the RSA100 number. :) However, when attempting to run ./factor.sh vs a custom RSA155 (512 bit) number I get the following error: "Max spot instance count exceeded"

Has anyone encountered this?

If it helps, I am running the current version of OSX. Thank you.

ok: [localhost] => (item={u'ramdisk': None, u'kernel': None, u'root_device_type': u'ebs', u'private_dns_name': u'ip-10-0-0-4.ec2.internal', u'block_device_mapping': {u'/dev/sda1': {u'status': u'attached', u'delete_on_termination': False, u'volume_id': u'vol-'}}, u'key_name': u'faas', u'public_ip': u'3510', u'image_id': u'ami-', u'tenancy': u'default', u'private_ip': u'10.0.0.4', u'groups': {u'sg-0ada3a6cf75': u'faas'}, u'public_dns_name': u'ec2-210.compute-1.amazonaws.com', u'state_code': 16, u'id': u'i-', u'tags': {u'launch_group': u'faas_master', u'Name': u'faas_master'}, u'placement': u'us-east-1a', u'ami_launch_index': u'0', u'dns_name': u'ec2-350.compute-1.amazonaws.com', u'region': u'us-east-1', u'ebs_optimized': False, u'launch_time': u'2019-06-04T17:27:29.000Z', u'instance_type': u'c4.8xlarge', u'state': u'running', u'architecture': u'x86_64', u'hypervisor': u'xen', u'virtualization_type': u'hvm', u'root_device_name': u'/dev/sda1'})

PLAY RECAP ***********************************************************************************************************************************************************************************************************************************************************************************************************************************************
localhost                  : ok=4    changed=2    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   

PLAY [launch ec2 instances] ****************************************************

TASK [include_vars] ************************************************************
ok: [localhost]

TASK [include_vars] ************************************************************
skipping: [localhost]

TASK [launch : Launch EC2 instance(s)] *****************************************

PLAY [launch ec2 instances] ****************************************************

TASK [include_vars] ************************************************************
ok: [localhost]

TASK [include_vars] ************************************************************
skipping: [localhost]

TASK [launch : Launch EC2 instance(s)] *****************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Instance creation failed => MaxSpotInstanceCountExceeded: Max spot instance count exceeded"}```

Multiple changes resulting in broken scripts

There are multiple issues, likely from recent changes on various platforms:

  1. cado-nfs repository is offline (scm.gforge.inria.fr/cado-nfs/cado-nfs.git)
  2. Ubuntu trusty images are no longer available (may have to bump the image filter up to xenial, e.g. ubuntu-xenial-16.04-amd64-server-20210928)
  3. ec2.py / ec2.ini have been removed from the official Ansible project. There are mirrors of it elsewhere, although using the old ec2.py script will fail when run against the latest Ansible version installed via pip. ansible=v2.9 looks like like a possible solution as this was the last that used ec2.py, although this also fails due to a prior reported issue in that release

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.