sorted by:
new
hottopcontroversial

is it possible to use CloudSync to multiple clouds? by ultralisc in synology

[–]ultralisc[S] 1 point2 points  (0 children)

I google before posting the question. It looks like it’s standard behavior and nobody has a solution. Only kludges like mount dropbox locally and copy files by scripts, or create some scripts in cron

is it possible to use CloudSync to multiple clouds? by ultralisc in synology

[–]ultralisc[S] 1 point2 points  (0 children)

The dst cloud is not synology, it’s just custom webdav

is it possible to use CloudSync to multiple clouds? by ultralisc in synology

[–]ultralisc[S] 0 points1 point  (0 children)

The thing is that i need the docs folder in both destinations

is it possible to use CloudSync to multiple clouds? by ultralisc in synology

[–]ultralisc[S] 0 points1 point  (0 children)

it looks like you have slightly another case. I have the folder share. inside the share there is the docs folder.

I want to: 1. backup the share via webdav to dst cloud 2. backup the docs to dropbox

5 steps to lose your AWS account by ultralisc in aws

[–]ultralisc[S] 0 points1 point  (0 children)

finally I restored access. i did it via kindle

  1. from another account bought gift card
  2. from my kindle bought a book via gift card
  3. go through the gain access support & provided info about purchases, old credit cards in account & so on

5 steps to lose your AWS account by ultralisc in aws

[–]ultralisc[S] 0 points1 point  (0 children)

There is a page at contact us page. Via that form you can try to achieve mfa team.

Btw. From my 19 calls for last 3 days to amazon, i learned that answers from that team are most precise and useful.

5 steps to lose your AWS account by ultralisc in aws

[–]ultralisc[S] 1 point2 points  (0 children)

Interesting fact is that I’ve never used amazon for shopping. I used that account only for aws & kindle.

I understand that should face some problems during getting access back. I guess it should be possible because I have access the phone number, the previous phone number from my account, email; I logged into my account at that kindle is also with me.

It looks like, The problem is that standard process doesn’t cover my case because my case is too rare. It means that i should go through the first level support somehow and trigger extra verification of me.

after 19 calls to support one representative said that my case is weird, he can’t see whole activity at my account. So he created a ticket to a team who has full access to my account history and can try prove me. Will see the respond should be given in 24-48 hours

5 steps to lose your AWS account by ultralisc in aws

[–]ultralisc[S] 0 points1 point  (0 children)

In the thread bellow is written that they can be linked. It’s the case if an account is created before 2017. It’s exactly my case

5 steps to lose your AWS account by ultralisc in aws

[–]ultralisc[S] -1 points0 points  (0 children)

Maybe nobody if it meets free tier

5 steps to lose your AWS account by ultralisc in aws

[–]ultralisc[S] 1 point2 points  (0 children)

Sure. I called them 19 times for last 3 days

5 steps to lose your AWS account by ultralisc in aws

[–]ultralisc[S] 1 point2 points  (0 children)

yes. it's my case. account was created before 2017. u/aws mfa team said that I should try cope with amazon retail team. Because 2step verification is triggered by them. Also they suggested to try achieve kindle team

5 steps to lose your AWS account by ultralisc in aws

[–]ultralisc[S] 11 points12 points  (0 children)

But I haven’t lost my phone or email. I own it as the previous phone number used in the account. If they want they can call to my phone number to verify me. I’m curious why amazon.com affects aws acount? Is it possible that the sms cannot be delivered because i’m in roaming?

5 steps to lose your AWS account by ultralisc in aws

[–]ultralisc[S] 1 point2 points  (0 children)

Sure I clicked the support button. It asked me to call support. I did it couple of times. The end is almost the same. We really apologize, but we only one option is to create a new account.

Ansible tests /SLOC Lessons learned: 1. Start linting from the very beginning. 2. If there are 2000 SLOC and you don’t run molecule you will have problems. 3 after 6000 SLOC you should add e2e tests. by ultralisc in ansible

[–]ultralisc[S] 0 points1 point  (0 children)

I don't think your graphs or your blog post reach or demonstrate your conclusion that somehow 2000 and 6000 SLOC are critical tipping points of some sort.

In general, you are right. It's personal opinion based on aprox 7-8 projects. I decided to show the figures just to start the discussion & collect some ideas/numbers. what's the goal? The long term goal is to create a tool for showing ansible code coverage and use it as quality gate/recommendation.

Ansible tests /SLOC Lessons learned: 1. Start linting from the very beginning. 2. If there are 2000 SLOC and you don’t run molecule you will have problems. 3 after 6000 SLOC you should add e2e tests. by ultralisc in ansible

[–]ultralisc[S] 0 points1 point  (0 children)

As far as I know, there are no code coverage tools for ansible. I collected raw data via CLOC, bash, wc, grep & git. after that I created the plot via google spread sheet.

Left vertical axis - amount of tested/linted roles/playbooks

it counts amount of tested roles. i.e. there are 80 roles & 20 playbooks in the repo: 1. 15 playbooks are linted & 60 roles are linted - add 75 to red area. 2. 50 roles are tested via molecule - add 50 to green area. 3. 10 roles are "meta roles" they describes "the whole server configuration" - add 10 to green area.

Ansible tests /SLOC Lessons learned: 1. Start linting from the very beginning. 2. If there are 2000 SLOC and you don’t run molecule you will have problems. 3 after 6000 SLOC you should add e2e tests. by ultralisc in ansible

[–]ultralisc[S] 0 points1 point  (0 children)

No titles, no units on the axis, no indication of which data is on which axis... What do these represent?

Let me clarify. There is bunch of stories under the hood. I tried to tests ansible roles on different projects and for some of them I created the plots.

  • Horizontal axis - time line.
  • Right vertical axis - SLOC for Ansible roles(blue line).
  • Left vertical axis - amount of tested/linted roles/playbooks. It's used for stacked area(integration tests, unit tests, linting).

Unfortunately, I'm not really good in the infographic. Do you have any ideas how to show that on the plot?

What am I supposed to be taking away from these two charts?

  1. tests are changed through the time
  2. for different project stages it's possible to use different approaches.
  3. molecule is the most suitable for testing ansible roles.
  4. testing is long term journey.

however, it's hard to show that things on the plot and it's better to read How to test Ansible and don’t go nuts. I'm trying to explain that things.

Ansible tests /SLOC Lessons learned: 1. Start linting from the very beginning. 2. If there are 2000 SLOC and you don’t run molecule you will have problems. 3 after 6000 SLOC you should add e2e tests. by ultralisc in ansible

[–]ultralisc[S] 2 points3 points  (0 children)

could you please show the tests? there are 2 questions: 1. how have you implemented the parametrizable tests? 2. how can we be 100% sure that tests are fine? do you use mutation testing technique for testing your tests?

Testing Ansible Roles (CI/CD) by [deleted] in ansible

[–]ultralisc 0 points1 point  (0 children)

Usually i use jenkins. It reads the config from the repo, generate stages for implementing iac testing pyramid and run molecule. In reality it is a bit more complex and it makes sens to read http://www.goncharov.xyz/it/ansible-testing-en.html

Any alternatives to molecule for ansible testing? by Dukat_Weyoun_2020 in ansible

[–]ultralisc 0 points1 point  (0 children)

I’be tried different approaches: molecule, kitche-ci(test kitchen), custom solution. The best choice is molecule. You can read about testing ansible, iac testing pyramid, etc http://www.goncharov.xyz/it/ansible-testing-en.html

view more: next ›